Tags
- language 2
- instinct 1
- windows 1
- oem 1
- key 1
- retail 1
- nodejs 2
- iojs 1
- writable 1
- transform 1
- streams 1
- rethinkdbdash 2
- bug 1
- thinky 1
- relation 2
- rethinkdb 1
- archlinux 2
- kernel 1
- encryption 2
- disk 1
- nginx 1
- proxy 1
- proxy_pass 1
- redirect 1
- localhost 1
- linux 1
- dual-boot 1
- softwareengineering 211
- worklifebalance 5
- wlb 6
- happynewyear 1
- job 4
- hopping 1
- context 1
- switching 1
- growth 33
- ai 6
- deepmind 1
- google 2
- alphageometry 1
- math 1
- monolith 3
- microservice 3
- goliath 2
- tinker 1
- tools 4
- hack 1
- environement 1
- cnil 1
- amazon 1
- privacy 6
- vim 1
- emacs 1
- editor 1
- AI 1
- mirror 1
- humanity 1
- rejection 1
- OK 1
- manager 1
- IC 1
- oncall 2
- quiet 1
- sleep 1
- interview 11
- question 2
- returntosender 1
- coding 6
- leet 2
- code 4
- hackerrank 2
- cut 1
- corner 1
- speed 3
- marathon 1
- listening 1
- patience 1
- empathy 1
- side 1
- project 1
- journey 2
- moonlighting 1
- small 1
- pull 1
- request 1
- breakdown 1
- boring 2
- tedious 1
- notinteresting 1
- work 3
- regulations 3
- fun 1
- company 1
- event 1
- softskill 2
- writing 3
- culture 3
- paranoid 1
- spam 1
- abuse 1
- system 2
- difference 2
- inferred 1
- data 4
- personal 1
- sprint 1
- teammanagement 1
- careerdevelopment 1
- growthtips 8
- promotion 8
- motivation 1
- gettingthingsdone 1
- stayhumble 1
- mentorship 3
- simpleisbetter 1
- investinyourself 1
- automation 2
- copilot 1
- process 3
- operationalexcellence 1
- managingup 1
- internationalwomensday 1
- biasawareness 1
- genderequality 1
- selfreflection 1
- timezones 1
- madness 1
- weekendwisdom 1
- ownership 2
- consulting 1
- careeradvice 1
- perspective 1
- insight 1
- culturaldifferences 1
- impostersyndrome 1
- growing 4
- knowledgesharing 1
- seniorengineer 1
- softwareengineering 10x productivity growing seniorengineer 1
- anonymity 1
- consent 1
- feedback 1
- stress 1
- responsibilities 1
- vision 1
- leadership 6
- reading 1
- books 1
- stack 1
- technology 1
- marketing 2
- celebrate 1
- promote 1
- naming 1
- machinelearning 1
- predictions 1
- inclusivewriting 1
- bias 3
- comfort 1
- challenge 1
- light 1
- office 1
- rto 2
- wfh 1
- appreciation 1
- others 1
- thankful 1
- movingforward 1
- fear 2
- breakingprod 1
- school 1
- industry 1
- academia 1
- leaving 2
- opportunity 1
- pto 1
- vacation 1
- timeoff 1
- newgrad 1
- internship 1
- experience 3
- jobhopping 1
- level 5
- title 1
- career 2
- faang 3
- manga 2
- happiness 3
- success 1
- alignment 2
- okr 1
- planning 1
- together 1
- life 1
- software 2
- properties 1
- design 3
- 3p 1
- opensource 1
- security 3
- TL 2
- adapt 2
- flexible 2
- conflict 1
- tension 1
- junior 1
- advice 1
- nojerk 2
- toxic 2
- test 3
- quality 1
- visa 1
- immigration 1
- abroad 1
- risk 5
- debugging 1
- education 1
- college 1
- seniority 1
- cruising 1
- escalation 2
- communication 14
- infrastructure 7
- foundation 1
- frontend 1
- backend 1
- stateful 1
- stateless 1
- semantics 1
- baddata 1
- techdebt 3
- fixit 2
- consistency 4
- stability 1
- horizontal 1
- edgecase 2
- prioritization 2
- worstcase 2
- userjourney 3
- notification 1
- boundaries 1
- trendy 1
- follow 1
- effort 1
- compliance 1
- api 3
- component 1
- layoff 2
- python 1
- golang 1
- skill 3
- resume 1
- promo 3
- peer 1
- senior 1
- fomo 1
- missing 1
- why 1
- mindset 1
- problems 1
- meeting 1
- focustime 1
- calendar 1
- compensation 3
- salary 1
- market 1
- perk 1
- benefit 1
- privilege 1
- thankyou 1
- mom 1
- mothersday 1
- hero 1
- ninja 1
- tdd 1
- testdrivendevelopment 1
- opinion 1
- principle 2
- toomanycooks 1
- greatness 1
- chase 1
- hungry 1
- prepare 1
- training 1
- jobhunting 1
- harm 1
- regulation 1
- monitoring 3
- logging 2
- metric 3
- alert 2
- offshore 1
- remote 2
- opportunities 2
- deadline 1
- help 1
- fix 1
- itsupport 1
- tshape 1
- error 1
- internal 1
- invariant 1
- script 1
- efficient 2
- mentalhealth 1
- opening 1
- requirement 1
- raisethebar 2
- structuredthoughts 1
- takethetime 1
- archetype 1
- ownpath 1
- blob 1
- unstructured 1
- schema 1
- id 1
- uniqueness 1
- metadata 1
- balance 1
- disagree 1
- commit 1
- killedbygoogle 1
- product 1
- shutdown 1
- extrapolate 1
- local 1
- number 1
- interpretation 1
- visiblework 1
- learning 2
- improving 1
- engineer 1
- income 1
- precarity 1
- simple 1
- noknobs 1
- idea 1
- controversial 1
- onepager 2
- leetcode 1
- duck 1
- refactoring 1
- evolve 1
- leading 1
- example 1
- dad 1
- dontworry 1
- learn 1
- healthy 1
- kindness 1
- instagram 1
- struggle 1
- sharing 1
- golden 1
- maintenance 1
- hiring 2
- recruiting 1
- performance 1
- pip 1
- improvement 1
- fired 1
- announcement 1
- behavior 1
- highpaying 1
- productivity 2
- slow 1
- debt 1
- delegating 1
- letitgo 1
- backdoorgrant 1
- cashflow 1
- scale 1
- ergo 1
- chronic 1
- pain 1
- longterm 1
- hackathon 1
- weeks 1
- good 1
- fast 1
- evolution 1
- hard 1
- outage 2
- incident 1
- hustle 1
- cultural 1
- bigtech 2
- doc 1
- functional 1
- programming 1
- imperative 1
- celebration 1
- reallife 1
- society 1
- attempt 1
- hardskill 1
- qualitative 1
- quantitative 1
- absolute 2
- relative 2
- percentage 2
- concise 1
- gettothepoint 1
- microoffice 1
- returntooffice 1
- story 1
- narrative 1
- humble 1
- completeness 2
- problem 2
- investment 1
- config 1
- optional 1
- defensivecode 1
- nontechnical 2
- canary 1
- testinginprod 1
- cascadingfailure 1
- thread 1
- starvation 1
- cascading 1
- failure 1
- rollout 1
- strategy 1
- slo 2
- sla 1
- overhead 2
- rollback 2
- safe 1
- execution 1
- iorwe 2
- staycurious 1
- openmind 1
- worldsyoudontknowexist 1
- polish 1
- tool 1
- invest 1
- workflow 1
- wellbeing 1
- climbing 1
- largeproject 1
- givingup 1
- believeinyourself 1
- newhire 1
- pride 1
- arrogance 1
- perfection 1
- laddertransfer 1
- qa 1
- switchingladder 1
- nosql 1
- monorepo 1
- spaghetti 1
- session 1
- chair 1
- managingout 1
- firing 1
- latency 1
- cost 1
- bigo 1
- tail 1
- comp 1
- calibration 2
- typing 1
- cognitive 1
- scaling 1
- yourself 1
- format 2
- waterfall 1
- iterating 1
- refactor 1
language
instinct
windows
oem
key
retail
nodejs
iojs
writable
transform
streams
rethinkdbdash
bug
thinky
relation
rethinkdb
archlinux
kernel
encryption
disk
nginx
proxy
proxy_pass
redirect
localhost
linux
dual-boot
softwareengineering
- Automatically format your code
- Refactor as you see fit
- Avoiding the waterfall process
- Opportunities-are-everywhere
- Scaling yourself
- Typing fast matters
- 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
- 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
- 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
worklifebalance
- Not sending emails outside business hours doesn’t improve work life balance
- Work life balance isn’t just about hours
- Growing and its cost on work life balance
- Oncall rotations should be quiet
- Health mind in a healthy body
wlb
- You don’t need to constantly learn or grow
- The unhealthy grind
- Work life balance isn’t just about hours
- Live for yourself
- Return to office
- Health mind in a healthy body
happynewyear
job
- About the jobs requirements
- The paradox of remote jobs and offshoring jobs
- Becoming a manager is changing job, not getting a promotion
- You should be thoughtful when job hopping
hopping
context
switching
growth
- Scaling yourself
- Joining promo sessions
- Joining promo sessions
- On (No)SQL being fast
- Your growth isn’t hindered by new senior hires
- You don’t need to constantly learn or grow
- Your title isn’t what prevents you from leading
- Understanding non technical interview
- Get to the point
- You don't necessarily need amazing soft skills
- Learning to let go of things
- You don’t have to be an A player
- Don't hide your struggles
- You can't build instagram
- The unhealthy grind
- Don't worry about what you don't know
- The hidden and misunderstood work
- Learn to extrapolate
- Carve your own path
- Strive to be the (improving) median
- About the jobs requirements
- Consistency doesn’t have to be uniform
- You don't have to overthink too much as a junior engineer
- Laarn to say no
- Joining FAANG and other top tier companies
- Getting experience as a new grad
- It's OK to leave
- Choosing between academia and the industry
- Which technology should you learn?
- Reading is not enough
- Giving feedback
- Look back to move forward
- You should be able to context switch with zero cost
ai
- The next high paying jobs
- Regulations should look at potential harm of data rather than its semantics
- Concerns around AI predictions
- AI will partially replace software engineers
- Introductin to privacy AI
- Alphageometry capabilities
deepmind
alphageometry
math
monolith
- You can scale a monolith
- You don’t have to choose between monolith and microservices architectures
- AI should be regulated now
microservice
- The problem isn't the monorepo
- You don’t have to choose between monolith and microservices architectures
- AI should be regulated now
goliath
- You don’t have to choose between monolith and microservices architectures
- AI should be regulated now
tinker
tools
- The infra engineer mindset
- Look beyond tools and technologies
- Create shortcuts, learn tools and build muscle memory
- t’s OK to be rejected
hack
environement
cnil
amazon
privacy
- Microsoft AI feature’s privacy fiasco
- What’s privacy infrastructure?
- Anonymization of data is misleading
- Inferred data should be regulated similarly as collected data
- Introductin to privacy AI
- The CNIL fined Amazon
vim
emacs
editor
AI
mirror
humanity
rejection
OK
manager
IC
oncall
quiet
sleep
interview
- Your title isn’t what prevents you from leading
- Understanding non technical interview
- Interviews shouldn’t be hard
- A good coding interview is more than writing code
- Interviewing people
- Training for code interviews
- The skills section shouldn’t be at the top of your resume
- The properties matter more than the name
- 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
question
returntosender
coding
- A good coding interview is more than writing code
- Getting credit
- Training for code interviews
- Adapt to your environment
- Coding interviews are fine and useful
- Layoffs are killing innovation in companies (and eventually the companies themselves)
leet
- Coding interviews are fine and useful
- Layoffs are killing innovation in companies (and eventually the companies themselves)
code
- First principles
- Write tests
- Coding interviews are fine and useful
- Layoffs are killing innovation in companies (and eventually the companies themselves)
hackerrank
- Coding interviews are fine and useful
- Layoffs are killing innovation in companies (and eventually the companies themselves)
cut
corner
speed
marathon
listening
patience
empathy
side
project
journey
moonlighting
small
pull
request
breakdown
boring
tedious
notinteresting
work
regulations
fun
company
event
softskill
writing
culture
paranoid
spam
abuse
system
difference
inferred
data
- Regulations should look at potential harm of data rather than its semantics
- Data suffers the most from software engineering technical debt
- Moving with vision
- Inferred data should be regulated similarly as collected data
personal
sprint
teammanagement
careerdevelopment
growthtips
- Adapt to your environment
- Adjusting to American peers
- Don’t assume incompetence
- Don’t go into consulting as your first job
- Look back to move forward
- Managing up
- Write code for people, not for you, not for machines.
- Becoming a staff software engineer
promotion
- Joining promo sessions
- Your growth isn’t hindered by new senior hires
- The hidden and misunderstood work
- Get promoted before switching job
- You don't have to overthink too much as a junior engineer
- You aren’t getting promoted when switching companies
- Growing and its cost on work life balance
- Becoming a staff software engineer
motivation
gettingthingsdone
stayhumble
mentorship
simpleisbetter
investinyourself
automation
copilot
process
operationalexcellence
managingup
internationalwomensday
biasawareness
genderequality
selfreflection
timezones
madness
weekendwisdom
ownership
consulting
careeradvice
perspective
insight
culturaldifferences
impostersyndrome
growing
- Write docs like you write (good) code
- Getting credit
- Don’t let the fear of breaking prod stop you
- You don't need to know everything
knowledgesharing
seniorengineer
softwareengineering 10x productivity growing seniorengineer
anonymity
consent
feedback
stress
responsibilities
vision
leadership
- Brilliant ideas are not enough
- Strive to be the (improving) median
- Fear of missing out?
- Finding a good manager is the most important
- Good leadership is flexible
- Moving with vision
reading
books
stack
technology
marketing
celebrate
promote
naming
machinelearning
predictions
inclusivewriting
bias
comfort
challenge
light
office
rto
wfh
appreciation
others
thankful
movingforward
fear
breakingprod
school
industry
academia
leaving
opportunity
pto
vacation
timeoff
newgrad
internship
experience
jobhopping
level
- ORMs aren’t just syntactic sugar
- Hiding your level is silly
- Get promoted before switching job
- Time seniority != Level seniority
- You aren’t getting promoted when switching companies
title
career
faang
manga
happiness
- You don’t need to constantly learn or grow
- Work life balance isn’t just about hours
- Live for yourself
success
alignment
okr
planning
together
life
software
properties
design
- You can't build instagram
- You must learn to think in terms of components and APIs
- The properties matter more than the name
3p
opensource
security
TL
adapt
flexible
conflict
tension
junior
advice
nojerk
toxic
test
- Golden tests are a hassle to maintain
- TDD is not enough (or not for what matters the most)
- Write tests
quality
visa
immigration
abroad
risk
- Should you go for promo?
- Security is all about risk
- Communication about risks
- Regulations should look at potential harm of data rather than its semantics
- Working abroad on a visa
debugging
education
college
seniority
cruising
escalation
communication
- Monitoring small slices
- Using “I”, “we” or
- Don’t be condescending (Crowdstrike edition)
- Get to the point
- Get to the point
- Good APIs break early
- Absolute and relative numbers
- Quantitative over Qualitative
- Building your foundations
- Don't hide your struggles
- Refactorign code
- Take the time to think
- Communication about risks
- Leadership escalations
infrastructure
- Building your foundations
- The hidden and misunderstood work
- Security is all about risk
- No hero policy
- What’s privacy infrastructure?
- Consistency in large infrastructure
- The struggle of drama free launches
foundation
frontend
backend
stateful
stateless
semantics
baddata
techdebt
- Refactor as you see fit
- Hackathons and fixit weeks are bandaids to deeper problems
- Data suffers the most from software engineering technical debt
fixit
consistency
- Automatically format your code
- Opportunities-are-everywhere
- Consistency doesn’t have to be uniform
- Consistency in large infrastructure
stability
horizontal
edgecase
prioritization
worstcase
userjourney
- Build simple stuff for normal people
- You shouldn’t always optimize for the global outcome
- Prepare the non technical interviews
notification
boundaries
trendy
follow
effort
compliance
api
- The problem isn't the monorepo
- TDD is not enough (or not for what matters the most)
- You must learn to think in terms of components and APIs
component
layoff
python
golang
skill
resume
promo
- Joining promo sessions
- Should you go for promo?
- Having senior peers is not what prevent you from getting promoted