Saadat

swe. Build. Solve. Create. Keep moving forward.

[Saadat @saadat_1997]

Day 0 (Sept → Dec)

Winter Arc begins

Goodbye npm install

Hello 👋🏻 public static void main(String a[])

Time to see what the enterprise world has to offer with Java

[Saadat @saadat_1997]

@ZaidBadgujar Awesome 🚀

[Saadat @saadat_1997]

Day 3 (Java Winter Arc)

- Input/Output, Debugging and Datatypes

[Saadat @saadat_1997]

Day 2 (Java Winter Arc)

- java architecture
- arithmetic, relational, logical operators
- if else conditionals, switch statements

coming from javascript, the syntax feels familiar which is nice
I don't really have to go through such basic concepts but sometimes you miss little syntax quirks so its better to just do it
For eg. there's a new way to write switch statements in java using the -> arrow syntax and you don't need to use break anymore, also you can return a value from it and store it in a variable

[Saadat @saadat_1997]

Day 2 (Java Winter Arc)

- java architecture
- arithmetic, relational, logical operators
- if else conditionals, switch statements

coming from javascript, the syntax feels familiar which is nice
I don't really have to go through such basic concepts but sometimes you miss little syntax quirks so its better to just do it
For eg. there's a new way to write switch statements in java using the -> arrow syntax and you don't need to use break anymore, also you can return a value from it and store it in a variable

[Saadat @saadat_1997]

Day 1 (Java Winter Arc)

- Java introduction
- JDK setup
- How Java works
- Variables, data types and literals
- type conversion

long way to go

[Saadat @saadat_1997]

Day 1 (Java Winter Arc)

- Java introduction
- JDK setup
- How Java works
- Variables, data types and literals
- type conversion

long way to go

[Saadat @saadat_1997]

Day 0 (Sept → Dec)

Winter Arc begins

Goodbye npm install

Hello 👋🏻 public static void main(String a[])

Time to see what the enterprise world has to offer with Java

[Saadat @saadat_1997]

@Hiteshdotcom They should add the calling feature and call it a retro phone
Ppl are not buying this for the software but rather the hardware which looks like a pokedex

[Saadat @saadat_1997]

why most developers never become tech leads:

• they optimize for being right instead of being effective
• they solve technical problems but ignore people problems
• they communicate in code when others need plain English
• they avoid conflicts instead of resolving them
• they think leadership is about having the best ideas

technical skills get you promoted to your level of incompetence

[Saadat @saadat_1997]

production deployment reality:

• something always breaks that worked in staging
• friday deployments are cursed but sometimes unavoidable
• rollback plans are theoretical until you need them
• monitoring tells you things are broken, not why
• hot fixes introduce more bugs than they solve

staging is not production no matter how hard you try

[Saadat @saadat_1997]

what senior developers actually do:

• prevent problems instead of just solving them
• translate business requirements into technical decisions
• mentor other developers through code reviews and pairing
• advocate for technical decisions in business meetings
• balance technical debt against feature delivery

leadership through technical expertise

[Saadat @saadat_1997]

developer burnout warning signs:

• dreading opening your laptop
• feeling nothing when code works on first try
• avoiding challenging problems
• checking social media constantly during work
• fantasizing about completely different careers

address before it becomes serious

[Saadat @saadat_1997]

technical interviews are broken but you still need to pass them:

• leetcode doesn't predict job performance
• whiteboard coding doesn't represent real work
• take-home projects favor people with free time
• system design questions test memorization not thinking
• cultural fit questions have hidden bias

play the game while working to change it

[Saadat @saadat_1997]

career advice that sounds good but doesn't work:

• "follow your passion" when you need to pay bills
• "network your way to success" without skills to back it up
• "fake it till you make it" in technical interviews
• "work at a startup for equity" when you need steady income
• "learn everything" when specialization pays more

context matters more than generic advice

[Saadat @saadat_1997]

tools that actually improve productivity:

• good terminal setup with aliases
• IDE configured for your specific workflow
• automated testing that catches real bugs
• monitoring that alerts before users complain
• documentation you can actually find when needed

invest in your daily workflow

[Saadat @saadat_1997]

developer impostor syndrome triggers:

• seeing 20-year-old startup founders on social media
• reading about someone's perfect development workflow
• hearing about salaries higher than yours
• watching conference talks about topics you don't understand
• realizing how much you still don't know

everyone feels this way sometimes

[Saadat @saadat_1997]

production incidents teach you more than tutorials:

• how to stay calm under pressure
• what monitoring actually matters
• why deployment rollback procedures exist
• how to communicate with non-technical stakeholders
• what corners you can never cut

crisis reveals true skill levels

[Saadat @saadat_1997]

salary bands companies don't want you to know:

• they have a range but anchor low
• location adjustments are negotiable
• internal promotions get smaller raises than job hopping
• equity percentages mean nothing without company valuation

transparency would fix a lot of problems

[Saadat @saadat_1997]

framework fatigue is real:

• new JavaScript framework every month
• each promises to solve problems you don't have
• learning curve costs more than benefits
• team knowledge gets fragmented
• hiring becomes harder when you use obscure tools

boring technology wins long term

[Saadat @saadat_1997]

debugging skills that separate seniors from juniors:

• read error messages completely before googling
• reproduce the bug consistently before fixing
• check what changed recently in the system
• isolate the problem to the smallest possible scope
• document the root cause for future you

systematic beats random

[Saadat @saadat_1997]

meeting types that waste developer time:

• daily standups that become status reports
• planning meetings without clear requirements
• architecture discussions with no decision maker
• retrospectives where nothing changes
• demos to people who won't use the product

your time has value, protect it

[Saadat @saadat_1997]

open source contribution reality:

• maintainers are overwhelmed and underpaid
• your first PR will probably be rejected
• documentation improvements are more valuable than features
• bug reports with reproduction steps are gold
• small consistent contributions beat one big one

help the helpers