Learning Quickly Q&A and Videos

In, Alex answered that the key insight behind rapid career growth is good communication.

He points the reader to the "Effective Communication for Software Engineers" course and some other resources.

I feel like a ton of effective communication is , and so finding a good way to teach it outside of observing those who are already good at communication in the context a job is tricky. Specific case studies could be really helpful. I think Alex's course and the other linked resources were a really good introduction to effective communication, but if this is the key skill behind great performance I want to learn more! I've put most of the tips and tricks that Alex taught into practice at my current job and it's really improved my performance and my managers' trust in me already. A huge mindset shift for me was that it's better to risk over-communication than under-communication; it's better to be aligned but slightly annoyed by receiving a lot of messages than not aligned.

My question is: What is a good way to go about building my effective communication skills? Are there more really high-quality resources you recommend for building good communication skills?

I am moving teams for the first time in my three-year long career and the team I am moving to is full of very experienced folks(15-20) with the least experienced person with 10 YoE. Some of these folks have also been in the same team for years. I will be new in the team as well as tech stack.

How do I create impact, learn from these people, be able to create my own identity and not be shrugged off as a "junior engineer" who is not given important tasks?

Any additional tips on how can I leverage this move as a fresh start? Like relationship with manager, team and my attitude towards the work?

I work at a pretty early stage startup and I've historically only done backend. There's been a lot of new scope on the frontend side and so I'm now having to start getting some of the frontend features working as well. But the issue is the codebase seems to be using a lot of the newer frontend techstack like next.js, tailwind CSS and redux and whatnot.

I've never written any frontend so I'm kind of starting from scratch. How do you recommend I tackle this?

I know the common taro advice is to learn by doing but given that frontend is almost a different skillset I'm not sure what's the best approach.

Should I spend some time watching lessons or tutorials or try and hack together a small side project or should I just learn as I go?

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?

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 :)

Heard this phrase many times, but would appreciate some elaboration/insights. Let's say I don't have ANY frontend experience in the past, but somehow get hired at a FAANG as a frontend dev. We know onboarding is already tough - meeting new people, understanding new codebase, etc. In the first few weeks especially, how do you manage so many things? You have to go through the onboarding challenges, and on top of that also ramp up on frontend. Isn't that too much to take on?

How to make sure I am performing well and learning new things quickly?

I have a question about doing self-reviews. I'm not talking about doing them in the context of a company's performance review. I'm talking about doing them totally for myself regarding my own personal development, including my job, side-projects, learning, etc. It might even include more personal stuff like health and fitness, relationships, etc.

I recall Rahul mentioning something about setting aside a half hour at the beginning of every week to plan the week and take stock of last week. I also believe he says something about doing a quarterly review.

My questions are:

1. What do these weekly and quarterly reviews looks like, i.e. how should I go about doing them?

2. Is there more than just weekly and quarterly reviews? i.e. daily, monthly, annual?

3. Do these reviews involve planning out the next week/quarter or is that a separate exercise?

4. Is there a difference between doing self-reviews/planning when it comes to work vs. personal career development vs. personal life? Or is the approach/process the same?

I know different people do different stuff and YMMV, I'm looking for good habits I might apply to my own life!

Thanks!

I have worked primarily on the backend, but my company now has assigned me features concerning our Android app, which is built mainly on XML for layouts & Java.

How can I get started on this, be productive & contribute effectively?
Thanks.

What does Alex Chiou read?

How does he think when he writes?

Is there a certain number of drafts?

Does he get someone to read it and give their thoughts etc?

When I read Alex's work, it makes me think better. I learn something new because I think - oh, I could also think this way. Oh, someone else can think this way. Oh, I learned something new.

Hello, I've seen the term "maintenance projects" (basically, projects where you do bug fixing most of the time) and green field projects (projects where you write code from scratch).

I've been told that the maintenance projects are generally the ones that you want to avoid since you won't learn much.

I didn't see this view against software projects on TARO, like to divide the projects in to these categories from a high level view and I was wondering if you guys can tell me more about this business view of the software projects.

Are there other categories besides maintenance and greenfield? How can I avoid maintenance ones or recognize them?

Layoffs are making me quite anxious. I understand job security might not really be a thing when it comes to big tech, but I do want to try pursuing employment security, if that makes sense. How do I "get good" so I can be a little more resilient when it comes to layoffs and employment? I'm not really sure where to start.

Hi,

I am a mid level engineer. Recently I was given a task which had a tight deadline. I started looking at the task and was stuck as the results from the code run were not as expected while testing. I was unfamiliar with this area of code so tried my best to understand the code and investigate the cause of unexpected result. I raised this with the team and also raised this as a blocker. I mentioned that I did not have confidence in going ahead with the task without understanding the cause of the unexpected results. My team was unhappy with this as the code has been working okay so far without any issues and the unexpected results were likely because of a gap in my understanding. The team assumed that I did not want to do the task whereas my hold up was not wanting to proceed without having a clear understanding of what's going on.

Should I have approached the situation differently? How to work with an unknown or hardly known area of code on a tight deadline?

I have had issues in the past with the team because of performance and other reasons. I have recently improved my performance but fear falling back to the old ways.

Thanks

Hi Taro Community,

I’ve encountered an interesting situation at my company, where I was the sole member in India until recently. In March, we hired an internal manager in India, whom I now report to. In our latest 1:1, he mentioned that I wouldn’t be assigned direct coding tasks possibly until September or October. For now, my work involves renaming elements within the codebase, and while I understand the rationale behind these changes, I’m missing out on more substantive coding work.

Given this context, I’m seeking advice on how to proactively engage with and understand our codebase. Without being assigned direct coding tasks, what are some effective ways to delve deeper into the code, learn its intricacies, and prepare myself for future assignments?

• Should I take the initiative to review and study different parts of the codebase independently?
• Could I propose small, self-initiated coding projects to demonstrate my understanding and initiative?
• How can I use this time effectively to ensure that when coding tasks are assigned, I’m fully up to speed and ready to contribute meaningfully?

Any tips or shared experiences on how to navigate this period would be highly appreciated.

Thank you for your help.

I don't have a CS degree but I am working as a junior engineer. I am currently in the process of learning software engineering concepts and building foundational knowledge of systems (haven't really gotten into it but that's my next plan).

With the whole AI frenzy going on, my attention keeps diverting from one area of focus to another. It's hard to prioritize the things that I want to learn, and I am getting quite overwhelmed. Why? Because I've 1 year of experience and as a result of this constant flip flopping, I don't think I have really gained foundational knowledge of a certain topic which is appalling.

I failed out of my computer science program at university for this exact reason - did way too many hackathons at the cost of gaining a foundational understanding of topics. I want to do things right this time and not fall for the same trap where I sacrifice becoming good foundationally.

Has anyone faced this issue before? Looking for some advice on how to manage expectations and learning to grow as a developer.

After finishing my Bachelor's Degree in Computer Science and and working as a Machine Learning Engineer for ~5 years I'm looking for something new. So far, I've been mostly focused on building software for real time systems, deployments, basic modelling, information retrieval (search) and troubleshooting "legacy" code and systems.

I'm now preparing for a new round of interviewing and I hope to make the jump to a highly paid job, possibly in the US (I'm based in Europe).

After assessing my skills and profile, I noticed that my data engineering skills are really superficial and I'm absolutely not confident in this area. E.g. I know basic SQL, but haven't build a data pipeline or ETL, I don't know hadoop etc.

Now, my question is if it would be wise to do Zach Wilson's  Boot Camp.

What I'd hope to gain from it: data engineering skills, more confidence in this area, and a higher chance of succeeding in (finding) a high paying job.

Do you think it's worth the investment, both in terms of time and money? Or do you think I should direct my focus elsewhere?

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.

I was watching the course on "" video from the coding course

As an MLE how narrow should my focus of a tech stack be? and what constitutes as a tech stack?

99% of my work is in Python, but at 1 job I did 90% of my work in PyTorch

At my current job I'm doing 40% sklearn/keras (it's a simpler version of PyTorch implementing same things, but is mostly used for ML stuff where models need low customization) + Pandas

Rest 60% of my job needed me to start working with Polars which is pandas but faster and is more heavy weight (similar to PySpark/Dask)

Is that too much branching? or Should I be narrowing my focus?

TL;DR it's ideal to hone in on 1 tech stack, but changing circumstances need me to use different frameworks depending on the problem. Is that bad?

With a background in hardware, firmware development and validation , I was able to get a master in MLE and transition to machine learning position, but my current machine learning role doesn't focus on building and deploying model but mainly on building infrastructure for machine learning which require a tech stack different from my previous experiences and background. Due to that, my code velocity is pretty slow and I'm also worrying that if I continue with that role, my machine learning skill will fade away or I won't able to build technical depth and be very proficient at machine learning. What do you recommend?

I have been looking to switch tech stacks for a while now and although i have made progress in upskilling, its quite a slow process. Work responsibilities always take over and leaves me little time for my own learning or side projects. Also i feel like there are tons of things to learn every single time i sit down. Could you help me with some tips to go about learning and deal with overwhelm when it comes to learning in tech?

Also, another reason this is hard is because the reward I get for spending more time on office work is immediate and helps me feel safe in terms of job security, but of course in the longer run it wont keep me happy which is why i need to spend more time on my education outside of work.

Thanks!