← sources

14 years, 8 jobs, 2 countries: what I'd tell myself at 22

source: reddit (reddit:developersIndia)published 2026-09-18 17:05ingested 2026-09-19 02:38

retained text

**Background:** Production engineering degree, graduated 2011 two years late, zero software knowledge. Paid for a training course, got a Java job in Pune in 2012. Since then: a startup, a finance shop, a telecom giant, a cloud startup, then seven years in the Netherlands doing platform and developer-experience work, and back to India in 2026. Ten things I actually learned, in rough order of how much they cost me.

**1. A gap in your record matters less than you think.** I have two missing years. People are surprised when they hear it, and that's the whole consequence. What you can show beats what you have to explain.

**2. Trial and error is a real learning method when you have no mentor.** Almost everything at my first job came from copying code, getting corrected in review, and breaking things. It's slow and it works. Don't wait for someone to teach you properly.

**3. Break production early, in a place that has backups.** I typed rm -rf /\* instead of rm -rf ./\* on a live box in my first job. A cron backup and a sleeping client saved me. The lesson wasn't "type carefully" — it was that a simpler sequence of commands has fewer ways to be wrong.

**4. "Over-engineering" is useless feedback unless you name the part.** I've heard it many times and been told which part maybe twice. If you say it, say which part and why; otherwise nobody learns anything, including you.

**5. Publish the small tool.** I wrote a Jenkins plugin in 2016 to fan in upstream jobs. It aged out within a year, and it's still part of why the next opportunity came. I wrote GitHub Action for feature in workflow that GitHub still doesn’t have natively after 5 years or so. Small public artifacts compound in ways your internal work cannot.

**6. Sideways growth is still growth, but notice when it's all you're getting.** More fullstack skills, some mentoring, no movement toward what I wanted to be. I spent too long not naming that.

**7. Good developer experience is poka-yoke, not documentation.** Turning free-text pipeline inputs into dropdowns with defaults isn't glamorous. The gain isn't saved minutes; it's the attention the form used to eat.

**8. In open, flat cultures you have to put yourself forward.** Stay quiet and you get short, simple tasks, because the long-running interesting work goes to whoever positioned themselves for it. I understood that about two years too late.

**9. "You lack power of influence" doesn't mean "you aren't famous."** I heard it that way for years. It means relationships, how you articulate a point, how you handle someone who disagrees, and walking into a hard conversation with a strategy you're willing to change mid-way.

**10. Going abroad isn't the finish line and coming back isn't failure.** Seven years in the Netherlands, a house bought partly to stop living in limbo, and then a decision to return. Both directions were ordinary decisions with tradeoffs.

One bonus, aimed at freshers: choosing an expensive training institute got me my first job and nothing else - no network, no fundamentals, no idea what software engineering meant. It was a ticket, not an education. Budget accordingly.

I wrote the long version of all this as a two-part retrospective on my blog; happy to share the link in a comment if that's allowed here.

document fetched 2026-09-19 00:24 · canonical https://reddit.com/r/developersIndia/comments/1wjvyp4/14_years_8_jobs_2_countries_what_id_tell_myself