Learning Quickly Q&A and Videos

My was “When given a take-home assignment, what is a reasonable turnaround time to get it back to them?” I now know it’s within a week.

I was given the assignment to create a basic Django app and was told to spend no more than 3 hours on it. Here’s the short text of the assignment description:

Table Metadata Extractor (Python)

Please provide a Python Django application that has one API endpoint which accepts a database connection string from your DB of choice (Redshift, BigQuery, Snowflake, MySQL, Postgres), connects to the database using and returns a list of the TableMetadata data objects (see below) for all tables in the database.

TableMetadata = {

columns: List[ColumnMetadata]

num_rows: int

schema: str

database: str

}

ColumnMetadata = {

col_name: str

col_type: str

}

Bonus points for:

·         Instructive error messages for improper connection strings or other invalid input

·         A solution that is efficient

As a Data Engineer/Analyst, I haven’t done web-dev stuff in years and have never used Django. My immediate instinct upon reading this project description was to find a resource to learn Django online. I’m not sure this is the right instinct, because software is about doing more than learning as Alex has mentioned so many times.

The way I see it, I have 3 ways to approach this assignment:

1. The way I just mentioned. Go down a learning path (hopefully not a rabbit hole), learn about Django and try completing the assignment.
2. Dive right in, try building the solution from scratch, Googling and ChatGPTing liberally.
3. Don’t do the assignment, spare myself the time and headache, and beef up my Python web-dev skills for the future.

The first approach requires the most upfront time. The second might be longer or shorter than the first. And the third doesn’t require any upfront time but requires a commitment to being in a much better position to do the assignment in future.

This is the second time in a couple of months I’ve been in this position since I was given an assignment for a different company to build a Flask app and did a shoddy job with it.

My first question is, which of the 3 options should I do to address this time-sensitive situation?

My second is, how should I address this situation long-term? Building some web-dev projects in Python with Flask/Django/FastAPI seems pretty logical. I don’t get to work with them at work, but I could spend a few weeks building stuff with them. I guess that’s the answer, the key is to avoid tutorial hell.

My third is, how should I think about take-home assignments in general? Should they stretch me a lot in terms of learning new things or conversely, should I be, say, 80% comfortable with what I need to do, just stretching a bit here and there to do stuff?

Thanks!

With learning other languages do you go straight into building or you have to learn some stuff first? I saw a video and the guy was like he just used Go getting started and just built as he go and learned way more from that than a tutorial. Cause there’s a CLI tool I wanna make with Go but I’m tired of the tutorial I just wanna build.

To put this into context, the question refers more to people who have already been at the company for a while, not onboarding engineers.

In my experience working only at startups, almost all learning has been the responsibility of the employee. There is a "spike" period where the engineer is given time to come up to speed, but it has always seemed to me a bit careless for managers to just give someone a list of technologies and say "learn this."

I guess this question is really a proxy for asking: how does FAANG approach "bootcamping" engineers on a new and important stack? Are workshops, training courses, and L&D actually effective? Suppose that I am a senior engineer who wants all the junior engineers in my team to learn how to use AI assist tools like Copilot, how would I approach making this mandatory if I really think it's a technology that's as crucial as git?

I am a new grad Software Engineer who has completed 6 months ago. There's a lot of internal tech stack and plenty of codelabs. Lately, I have realised that I am not prioritising learning about the stack my team uses (but I do not currently use directly).

I understand it would be helpful in one-off occasions when I have to interact with a new part of the codebase or during on-call, which I am expected to begin soon. However, I always end up prioritising my current work that I have in hand. (It is also because of the fact that I find the codelabs pretty slow and boring)

How should I prioritise learning new things? I remember Rachel's video where she said she spends 20% of her time learning new things and that seemed like a good strategy to me.

Everyone on my team is significantly more experienced than me. I feel a bit intimidated criticizing the decisions that engineers far more senior than me are making. How can I start contributing?

I'm a Staff Engineer in the satellite telecommunications industry where I am responsible for the strategic success of the software products in my department. My organizational responsibilities and weekly calendar align almost perfectly with the . I'm sure that it will come as a surprise to no one that getting to this point in my career was an intense and conscientious journey. I am self-taught, I fell in love with programming as a child, and I have never attended a University. Things are not even close to perfect, but I am happy with my career so far.

My day-to-day work does not involve much programming, but I spend the vast majority of my time communicating with Tech Leads, Scrum Masters, PMs, TPMs, EMs, etc. to coordinate and accomplish different tasks. The rest of my time is split between communicating and aligning with high-level product stakeholders, such as my boss, and mentoring engineers. When I do code, it is because there is some experiment I want to run, i.e., I might create a prototype of a new product or feature that could massively impact a departmental OKR.

Outside of my day-to-day work, I dedicate as much time as I can to learning and practicing new technical (programming, cloud), professional (LinkedIn Learning), and domain-specific (satellites, AI) skills. I also consume a lot of content here on Taro and I often participate in company and community programs that I believe in (change maker programs, diversity and inclusion programs, etc. as a participant or as a coach).

I would love to have input on this aspect of my career as a Staff Engineer who would like to be a Fellow one day. As I make progress in my career, I find that (obviously) the expectations others have of me, in regard to being at the forefront of technology and really knowing what I am talking about in domain-specific (science-heavy, business-heavy) topics, have grown exponentially. I've already adapted my approach to developing domain-specific skills, for instance, instead of relying solely on MOOCs, I also now have regular sessions with domain experts (business folks with advanced industry-relevant university degrees), something my boss encourages and expects me to continue to do. I have now also considered the prospect of going to university myself, something my employer would sponsor.

So the question is, how can I best invest my personal development time so that as I progress in my career I can continue to meet, or even surpass, exponentially growing expectations?

I'm sure someone will have a great idea of how to approach this challenge. Also, there is a quote I appreciate from Alex Chiou that gives me hope that I can do it.

It wasn't due to natural talent or anything - I'm honestly not that smart.

I find myself in this confusion as to how and when should I spend time in

1. Interview prep for FAANG or alike(I usually spend 2-3 hours everyday 7 days a week). This includes system design prep too.
2. Learning more about technologies such as and not limited to say kubernetes, new AWS services or preparing for AWS certification? or Docker etc.
3. Learning about ML, or say web 3 etc.

How should one spend time in making sure they are doing deliberate practice for the interviews, but also are in "sync" with the market with all the new tools and technologies out there? Where does one stop? I know my priorities, but I also feel i might loose focus on my interview prep if I start multitasking.

How do senior engineers or mid-level engineers keep themselves uptodate? or do they only learn "whatever is required to get my job done"?

How can I map out what to do in the first 90 days in a new role (staff and senior staff) and a new job (given factors like new codebase, new processes, people, and work ethics), especially when the domain and coding language are also new?

• Company is doing an AWS migration (with lambdas). We're moving away from old IBM architecture.
  • Goal is to move away from SOAP service to build scalable REST API.
• I have limited working experience with AWS but never touched Terraform or have needed to do any migration work at all.
• We'll be building out lambdas and transferring traffic over to our new service
• Team is also new to NodeJS (with the exception of some new folks i.e. me and some other people)

Any recommendations on how to best succeed given the current context?

• General recommendations for succeeding in this ambiguous domain?

• Resource recommendations?

Thinking of skimming AWS docs / AWS course to quickly learn basics but planning on spending most of my time on implementing lambdas with mock data -- goal is to share POCs with team and iterate on feedback before sharing our new service with stakeholders.

So i'm a entry level engineer and was reading some post on twitter about getting deeper in CS to be taken seriously. The post mentioned learning a lower level language and I always wanted to learn C++. But when i asked my friend who is senior that then went on to become a CTO at his own company he told me I should learn java since it's low enough that a lot of systems are built on it which in return means more jobs. When I looked at job listings for both languages there were fairly the same amount of job postings but he's saying it would be easier to get in entry level with java and that C++ is more for mid and higher levels. also i always wanted to learn C++ because i saw that with python is mainly used at hedge funds which eventually in my career i always wanted to join one, so which one should I choose? And please make a choice for me lol and not respond with "whatever you feel like doing", because i'm kinda indecisive with this choice.

What are some good resources and learning methods to become a back-end engineer in Node.js?

The benchmarks I am setting here are people like Robert Martin, Martin Fowler, Venkat Subramaniam (known for agile and Java), Guido Von Rossum (developed Python), Jeff Dean, Sanjay Gehlawat etc.

Latter two are Senior Fellow at Google. Up until a certain point, I understand that promotions are about the scope of impact inside an organisation, but how do you grow yourself outside the walls of it so as to be on your way to be extremely good in your craft and among top software engineering contributors in the world.

Would appreciate answers from as many folks as possible.

Hi Everyone,

I am a senior software engineer in my company. We are an R&D company who work for the retail industry. I work in the Computer Vision and systems area.

I joined this company as a senior software engineer. Initially, the project that I was hired for had C++ work but that project was scrapped and we worked on a new product where everything was Python and lots of DevOps tools.

Now the problem that I am facing is all my colleagues who are software engineers know a lot about Python and these tools. I have never used them so far. For me, it was exciting that I was using these new tools which were very necessary in the current industry but I was anyways slow and my code quality and the way I designed things never matched the team's ways of things. I know everybody says that the fundamental principles are the same but I found there are some pythonic ways which are way better than a person who is learning it. Additionally, I was a Senior Engineer, so the manager and lead always came to me and said that they expected more from me. I was not contributing enough.

I feel it is normal to expect things from me as I am a senior. The main problem that I face is I don't feel myself important to the team. Most of the development or coding is done by the rest of the team. I even see they are given more design and senior role work too. I am given very small things. Honestly, even I don't know if I will be able to work on designing systems using these technologies. It affects my confidence and so I am never confident in my work, I have a constant fear that I can lose my job anytime. I don't feel proud of my work anymore now. I have learnt the new tools from last 1 year but I am unable to lead the team in any direction. There are some new concepts in Computer Vision world now like Embeddings which is completely new to me I am struggling to catch up on anything.

Our product is going live very soon, so the issues and pressure have started to grow. I am not even able to build any relationships with the real stakeholders in the team. They all love my other teammates and thus keep giving them work. Whenever I try to talk to them about any issues I do not get any encouraging reply, it feels like I am giving very basic suggestions.

Can anyone advise me on how to handle and perform well in the team and above all feel recognized in the team and organization? I am pretty sure many people here would have changed technology and should have faced similar situations , many would have recovered from this situation.

I always have very high standards for myself and have always been recognized as so in my previous companies. Lately, I feel I am not feeling very proud about my work, and I feel that is the main issue. I need some advice to improve in my field and in a consistent way.

I recently got an offer for a Senior Java developer. While the interview rounds were mostly language agnostic, I know the basics of Java and can debug a Java program quite easily.

Not sure how much of the language depth should be adequate for a senior engineer. I've been a C++ engineer for sometime now.

How do I learn Java fast and efficiently? I'm aware that most of the learning will occur in the job itself, but I want the onboarding (a week away) to be as smooth as possible.

My question is when should I reach out to help someone. If someone new joins, and if it is clear that task might be difficult for person, or there is some context needed etc, and they fail to ask, should you help them? Reaching out early and helping might be hampering their own learning, also at risk of hurting someone's ego. But If I am in other person's shoes, I would appreciate all help so what is right balance here?

Also, should you helping be more visible or private? If it is public, other people can add extra context as they like, but maybe in private conversations, person can ask more follow up question, assuming they are afraid to ask dumb questions. To be more specifically, by public I mean team channel in slack and private would one-one chat.

Hi all, what are some of the book recommendations for career growth at tech companies..

1. early grad

2. 2 years experience at FAANG companies

3. Engineers at the age of 50+

Thanks!

One thing that I learnt in one of the taro videos is to choose the right project for the career growth. However, I lacked this kind of vision/ability to evaluate. What I can do to improve this weakness? Should I grow more engineering domain knowledge or should I take some business courses to further improve myself?

This question always stresses me because I'm a backend Python developer and the stuff I could learn is a lot that I end up studying/practicing nothing.

I use in my day to day: Python, Flask Docker, and Oracle. I don't know what else I could study or if I need to get better at these technologies.

Some engineers like to code, some like to manage projects, some like to stay close to the users. Software Engineers come in all shapes and sizes.

What are the major archetypes of Software Engineers and how can one identify one's own archetype to double down and improve.

This isn’t really a career question but does anyone have a good recommendation for resources to learn ios app development for a complete noob? I have a lot of experience building backend distributed systems, but other than building one android app back in college 6-7 years ago as part of the coursework, I haven’t really done any mobile app development ever.