Learning Quickly Q&A and Videos

I have recently joined a team which works in Go (no frameworks). My team handles multiple backend services ( exposed through REST APIs ) which are like a platform for various other services. I have picked up the language grammar and have enough understanding to write working code. However, I feel I don't "get" it. I don't understand how to organise the code into a well-defined folder structure and interfaces. I would like to understand what are some of the good ways to learn a new language. It's been 2 months since I started learning it and feel like I am working with incomplete knowledge. Maybe at 50% level. I know there's no point in understanding all the features of a language but I would like to understand design patterns, best practices and how to write high-quality code. I really need to be able to ramp up in another month's time. Majorly need advice on Learning to write high-quality Go code Writing with Dependency Injection in mind Design patterns and low-level system design

How can we identify what are the core in-demand "Legos", especially in the context of what we do commonly on our day to day job? As software engineers, we are tackled with new things to build regularly, so I was wondering how I could focus on the components (i.e. "Legos") that are built more regularly and learn to build them with high-quality. I don't have a concrete need for this right now, but I want to be more efficient at work and keep this in mind for when I do get into a new technology. As a web dev, a core in-demand Lego will be like responsive design or something like that right?

Hello, I am working as an Entry level engineer at mid size product based company. In my end year performance review, I got a feedback that I can work on improving my debugging and technical skills more. As well as, knowledge of other features and overall product as a whole would need to be increased as well. My Tech lead has offered to mentor me by conducting 1:1 sessions to help me improve at debugging and help identify patterns and teach basic principles. 2 other senior engineers on the team also reached out and offered to conduct sessions regularly with me, for which I am really grateful. For more context, all my teammates work remotely, so it is not beneficial to go to office. My question is, how can I best utilize these sessions with the senior engineers on team to improve more and skill up? That is, what kind of preparation/ questions should I have ready to make the most of these sessions?

Hello, I asked about this before, but it’s a bigger dilemma now as I’m actively interviewing and many top roles seek a software engineering background. Scenario: This past year at an AWS Cloud Consulting Partner, I built cloud and Terraform skills but had little software engineering experience. I dabbled in a few languages but haven’t committed to one. I want a versatile, productive, “startupy” language for an ambitious one-man project (possibly a PWA) that fuels learning, supports entrepreneurial goals, and offers a great dev experience. What I Enjoy: I love game dev with Godot, but GDscript has no job market. So, I’m considering a scalable full-stack CRUD project like a PWA game site (think ) that I can build solo. I want to master one language and framework — no constant framework-hopping like with JavaScript. Here are my main options: 1. Ruby on Rails – Productive, “batteries included,” and fun (so I hear). While some call it “dead,” remote roles (like GitLab) still exist. I worry about it being a risky specialization. 2. Blazor + .NET Core – Full-stack with one language (C#) and “batteries included” features. Blazor is new, but .NET Core skills stay relevant. I dislike JavaScript’s endless framework churn, so Blazor’s stability is appealing. 3. Golang – I like its “one way to do things” philosophy, compiled binaries, and cloud reputation. But it’s focused on microservices, not full-stack projects. I’m unsure if I’d stay motivated building APIs instead of an end-to-end product. Python feels similar — powerful but maybe not a “do it all” full-stack option. The Goal: I need speed, productivity, and specialization in a language worth mastering. I want to build a PWA project that teaches me core software skills fast and makes me marketable for software engineering roles. What would you recommend?

Hi, I'm currently a software engineer 1 working with a senior engineer trying to ship a new feature. The way it works, the senior engineer I work with has outlined the technical problem, scope, and approach we're doing. She has assigned the tasks and most of it (BE/FE) will be done by the senior and the portion I'm doing involves a BE service I've worked on before. Our deadline is in a month, as I'll be going on leave. I wanted to do a portion of the FE just to learn more about frontend technologies and was assigned tickets, however my senior engineer has started work on these and it looks like most of the work I'm going to be doing, apart from my tasks, are going to be reviewing/testing my senior engineer's PRs. I've worked with this part of the product before but I was hoping to get more exposure and practice. I was hoping to really learn more about the frontend aspects of our product so I'm a bit disappointed but I'm wondering maybe if my expectations (which was to learn more about FE) are unrealistic and perhaps unnecessary. As a new grad, what is the expectation from senior engineers? Do I communicate this to our manager or should I re-adjust my expectations?

What's the best way to upskill oneself in emerging fields? for example, what would be the most effective and easiest way of upskilling in Data & AI projects in absence of any direct work opportunities that involve those fields?

Preface: I might sound a bit critical at some points, but I’m asking this question with the intention of learning, not to demean others as this question has been on my mind for a while. A big reason why people join startups is that at startups you learn faster than you would at big tech. What’s not clear to me though is how this actually translates to having a successful career (especially when transitioning to big tech). Specifically, how does “learning more” in startups/getting more scope in startups translate to “materialistic” rewards such as TC, getting into big tech, getting senior swe faster etc.? I've seen Seed’s presentation about . He’s clearly achieved amazing things at Klaviyo, but at least from his LinkedIn profile, he joined Meta as an L5 (senior swe) with 4 yoe - couldn’t you achieve this result simply by working at Big Tech for just as long? If that’s the case, then what’s the point of joining a startup? I’ve watched Taro’s masterclass on choosing a good company (and many other startup-related videos on Taro), and for the pros for startups - specifically getting more scope - seems very superficial. Similarly, the cons for big tech (the inverse of startup pros- harder to find scope) seems also superficial.

What’s the best way to learn really good front end engineering? Specifically what frameworks / languages are useful, design patterns, and some projects to get hands dirty? my motivation for learning front end is to build products that people would actually use :)

I am a frontend focused full-stack engineer with 7 years of relevant experience in the frontend engineering space and a total of 12 years of experience. I am not able to decide where should I invest my time when working on side projects. Should I start picking up mobile (Android/iOS) or continue to sharpen my skills in the frontend development space? To put it another way, should I invest my time in going deep in my current domain or should I invest time learning mobile UI development as that has gained more traction and is viewed as more valuable skill? I think I am unable to decide whether to go about developing my skills in breadth or depth.

On most projects that I worked it was enough to have a high-level of how the higher picture of the code works and for the most tasks it was enough to copy paste and adapt existing code and for debugging it was also enough to have grasp the high level image.

However, I worked only on maintenance projects, that weren't very innovative. In order to have the chance to work on a good project how well should I know the tech stack?

For example for the stack: java/spring/elasticsearch/kafka/AWS, should I know the newest annotations or how the framework works under the hood, and probably be able to extend the framework, how to debug machine on VM etc?

Is there any sort of metric with respect to how in depth you should know your tech stack? Because in order to write code in a tech stack you don't need a lot of time to learn if you know the basics, but to write state of the art code I feel like you need years.