All blogs / Engineering management / careers
blog.justonepixel.com
Engineering management / careersSoftware / engineering practice
- Posts
- 227 from 21 Sep 2013 to 13 Jun 2025
- Posting
- now and then
- Kind
- personal blog
- Feed
- https://blog.justonepixel.com/atom.xml
2025 11
- What’s the hardest thing in software engineering?
- Longer design doc doesn’t mean better docs
- The cost of high seniority
- Learn data manipulation
- The importance of your initial promotions
- Automatically format your code
- Refactor as you see fit
- Avoiding the waterfall process
- Opportunities-are-everywhere
- Scaling yourself
- Typing fast matters
2024 207
- Get multiple mentors
- ORMs aren’t just syntactic sugar
- Hiding your level is silly
- Joining promo sessions
- Joining promo sessions
- Joining promo sessions
- Joining promo sessions
- The problem isn't the monorepo
- On (No)SQL being fast
- Joining as a QA engineer
- Be proud but not arrogant
- Your growth isn’t hindered by new senior hires
- On facing massive problems
- Correlation is not causation
- Climbing into FAANG/large tech companies
- Polish your workflows
- Worlds you don't know exist
- Monitoring small slices
- Using “I”, “we” or
- You don’t need to constantly learn or grow
- Brilliant ideas are not enough
- Keeping rollback safe
- Ownership is critical for efficiency and quality
- Understanding SLO
- Slow rollouts don’t add benefits
- Thread starvation and cascading failure
- Your canary won’t always save you
- Your title isn’t what prevents you from leading
- Understanding non technical interview
- Limit optional/nullable values
- The infra engineer mindset
- Mistakes and hard times level you up
- The completeness problem
- Don’t be condescending (Crowdstrike edition)
- Get to the point
- Micro offices
- Get to the point
- Good APIs break early
- Absolute and relative numbers
- Quantitative over Qualitative
- You don't necessarily need amazing soft skills
- Should you go for promo?
- Staying down to earth with software engineer compensation
- Celebrate people moving on
- Functional programming considered harmful
- Write docs like you write (good) code
- Opportunities in boring domains
- The culture of hustling
- Building your foundations
- Interviews shouldn’t be hard
- The untouchable code
- Hackathons and fixit weeks are bandaids to deeper problems
- Learn for the long term
- Get your ergo setup
- You can scale a monolith
- The myth of compensation bands
- Learning to let go of things
- Good processes are light
- You don’t have to be an A player
- The next high paying jobs
- The toxicity of asking for announcements
- PIPs aren't primarily meant to fire you
- Biases in recruiting
- Golden tests are a hassle to maintain
- Don't hide your struggles
- First principles
- You can't build instagram
- The unhealthy grind
- Don't worry about what you don't know
- Leading by example
- Refactorign code
- A good coding interview is more than writing code
- Executing large controversial ideas
- Build simple stuff for normal people
- The paradox of high income and financial
- Getting credit
- Interviewing people
- The hidden and misunderstood work
- The meaning behind numbers
- Microsoft AI feature’s privacy fiasco
- Learn to extrapolate
- Google killing non successful products is the right move
- Disagree and commit
- Security is all about risk
- Augmenting ids
- Blobs are your ennemy
- Carve your own path
- Take the time to think
- Strive to be the (improving) median
- About the jobs requirements
- Automating tasks
- Monitoring internal errors
- Being asked to fix computers
- Communication about risks
- The paradox of remote jobs and offshoring jobs
- The benefits of doing things well
- Building monitoring
- Regulations should look at potential harm of data rather than its semantics
- Writing for fun
- Get promoted before switching job
- Training for code interviews
- Pursuing greatness
- Having strong opinions
- TDD is not enough (or not for what matters the most)
- No hero policy
- Being privileged
- Evaluating perks
- How compensation works
- Being thoughtful about your time
- Look beyond tools and technologies
- Fear of missing out?
- Having senior peers is not what prevent you from getting promoted
- The skills section shouldn’t be at the top of your resume
- Google laying off its python team
- You must learn to think in terms of components and APIs
- What’s privacy infrastructure?
- Consistency doesn’t have to be uniform
- Don’t blindly jump into what’s hot
- Not sending emails outside business hours doesn’t improve work life balance
- You shouldn’t always optimize for the global outcome
- Prepare the non technical interviews
- Consistency in large infrastructure
- Don't just complain, fix the problem
- Data suffers the most from software engineering technical debt
- Backend engineers who look down on frontend engineers are wrong and short sighted
- The struggle of drama free launches
- Leadership escalations
- Time seniority != Level seniority
- Don’t underestimate going to college
- You can’t just compare outcomes
- Working abroad on a visa
- Write tests
- No jerks, no exceptions
- You don't have to overthink too much as a junior engineer
- Not all conflicts are unhealthy
- Finding a good manager is the most important
- Good leadership is flexible
- You shouldn't use third party software
- The properties matter more than the name
- Work life balance isn’t just about hours
- Aligning team priorities
- Live for yourself
- Laarn to say no
- Joining FAANG and other top tier companies
- You aren’t getting promoted when switching companies
- Getting experience as a new grad
- Unlimited PTO
- It's OK to leave
- Choosing between academia and the industry
- Don’t let the fear of breaking prod stop you
- Appreciate other people’s work
- Return to office
- Searching outside your comfort zone
- Use inclusive writing
- Concerns around AI predictions
- Market your work
- Which technology should you learn?
- Reading is not enough
- Moving with vision
- Growing and its cost on work life balance
- Giving feedback
- Anonymization of data is misleading
- The reality and misconception of 10x engineers
- Adapt to your environment
- You don't need to know everything
- Adjusting to American peers
- Don’t assume incompetence
- Don’t go into consulting as your first job
- Run away from time representations (and timezones)
- Look back to move forward
- Happy International Women's Day!
- Managing up
- Staff your processes and get rid of them
- AI will partially replace software engineers
- Create shortcuts, learn tools and build muscle memory
- Write code for people, not for you, not for machines.
- Stay humble
- Plan something for tomorrow
- Becoming a staff software engineer
- Two weeks sprints are terrible, period
- Inferred data should be regulated similarly as collected data
- Multiple systems working
- Be paranoid
- Sharpen your writing skill
- Attending company “fun” events
- Introductin to privacy AI
- The majority of the work is boring
- Write small pull requests
- Side projects are about the journey, not the results
- Listening is an underrated skill
- Don’t always cut corners
- Coding interviews are fine and useful
- Layoffs are killing innovation in companies (and eventually the companies themselves)
- Don’t miss on your opportunities when being interviewed
- Oncall rotations should be quiet
- Becoming a manager is changing job, not getting a promotion
- It’s OK to be rejected
- AI isn’t the mirror of humanity
- You should become proficient in vim or emacs
- The CNIL fined Amazon
- t’s OK to be rejected
- You don’t have to choose between monolith and microservices architectures
- AI should be regulated now
- Alphageometry capabilities
- You should be able to context switch with zero cost
- You should be thoughtful when job hopping
- Health mind in a healthy body