If you always chase a roadmap, you are just continuing the behavior of sticking to a predefined syllabus from your school days, when it was discouraged to go beyond it. I understand that roadmaps provide a sense of comfort and a structured and clear way to achieve something, but if you are focused on doing the bare minimum, then you 1. are at risk of developing a shallow understanding 2. miss the opportunity to stumble upon something amazing More importantly, you are robbed of experiencing the joy of learning something super interesting. Some of the most interesting and helpful things I know happened because I went out of the way and spent days understanding the nuances. To be honest, going out of the syllabus forced me to dig deeper because I started exploring it out of curiosity and genuine interest and not because of some peer pressure. I was driven by intrinsic motivation rather than an external impulse. I personally believe that deeper understanding is what separates good engineers from the better. By not sticking to some predefined roadmap, you 1. become comfortable with uncertainty and change 2. learn how to navigate through errors quickly 3. build an ability to learn any and every concept 4. become great at connecting the dots 5. and most importantly, you learn how to learn. Again, I am not telling you to abandon roadmaps entirely. They are useful guides, especially when you're starting out. The key is to use them as a starting point, not an endpoint. Let them not limit your learning and curiosity. You excel when you dare to differ. Hope this helps.

Hustle culture optimizes for input (work), not output (impact). It is okay to put in long hours. It is okay to sacrifice things for your goal. But do not waste effort optimizing theatrics. Put your effort into things that actually matter, things that move you closer to what you really want. If you do not know what you want, get that clarity first. Your goals cannot be a copy-paste of someone else's goals. You succeed only when you put effort in the right direction, at the right time, on something you genuinely care about. If you are seeing a dead end, switch. You cannot and should not be perpetually delusional. Hope this helps.

Months of building and shipping AI systems made me realize - one thing that makes agentic workflows work is good old best devops practices. If you do not have proper tooling, clean (and also well-defined) processes, and ephemeral environments set up, an AI agent cannot run or help you reliably. Be it agentic SDLC, running evals, phased agent rollouts, circuit breakers, database access, or anything else. Think about what an agent actually needs to do good work. It needs a safe place to run code, a fast feedback loop to know if something broke, and clear boundaries between development, staging, and production. Most skip this and go straight to "let the agent write and deploy code." Then they hit weird failures, lose trust in the system (and even AI), and quietly give up on agentic workflows altogether. The fix is not about AI at all. It is the same old devops discipline that made human engineering teams reliable in the first place. Good things die hard :)

if you are a curious engineer, it is so difficult not to have fomo. every other domain seems interesting every other book seems worth reading every other problem seems worth solving every other project looks like the next big thing every other framework feels like something you should learn. literally every single thing is a distraction. imo, there is no way to even deal with that.