All blogs / Engineering management / careers
Dan Dreams of Coding
Thoughts, stories and ideas.
Engineering management / careersSoftware / engineering practicePerformance / optimization
- Posts
- 209 from 9 Nov 2012 to 28 Oct 2026
- Posting
- monthly (17 in the last year)
- Kind
- personal blog
- Feed
- https://www.dandreamsofcoding.com/rss/
2026 17
- Time to Move On
- Switching to Ghost
- What Happens Next
- No Buts
- Advanced Technical Topics: Orchestration
- Advanced Technical Topics: Idempotence
- Category Error
- Lead Pipes
- The Wave of the Future
- Negotiating Vendor Contracts
- The Reckoning
- Thinking (and Hiring) in Bets
- Trust me, I know nothing
- The Big Mac Coding Era
- Understanding Performance
- Lucky
- How to improve team velocity, and why you won't
2025 2
2024 1
2018 2
2017 5
2016 21
- Boomerang
- How to make an introduction
- Negotiating for time
- Starter AWS stack
- Can't you make the team work harder?
- Hiring Engineers
- The PERN stack
- Managing rapid growth
- On not knowing
- Special Skills
- Ownership
- Closing shop
- AWS: a case study
- Full-stack Javascript
- Analytics First
- Startup year one: Building a great team
- The Tyranny of the P1
- Linux commands: partitioning, formatting, and mounting a drive
- Linux commands: cut and tr
- Linux commands: find
- Then and now
2015 22
- Doing the dishes
- How to set up the Android Emulator on a Mac
- Balancing your party
- Cleverness kills
- The parable of the 56k modem
- Three simple cooking hacks
- The Technologist's Dilemma
- Startup log: first impressions
- Monetizing failure: March/April 2015 report
- That's why they call it work
- Startup operations priorities
- Someone just quit
- Reflections on a year in DevOps
- Goldilocks process
- Customs
- Monetizing failure: February 2015 report
- is-a vs. has-a
- Monetizing failure: January 2015 report
- Three numbers
- Taking the long view
- Dissecting an interview question: math is hard
- Java quirks and interview gotchas
2014 31
- Things I hate, things I like
- Why big companies slow down, and what to do about it
- Special Roles: a Bestiary
- Three Nations
- Positive Feedback
- The Rules
- What annoys us defines us
- Running from bullets
- Knowing and Learning
- Dissecting an interview question: reconstructing a tree
- Making the end of your internship count
- What not to do during an interview
- Beads on a string
- Science, superstition, and open plan offices
- Shame is good
- Personal Favorites
- Your experience is not representative
- Infrastructure improvements
- Responsibility: a lament
- What makes a good interview question
- Dissecting an interview question
- Operations curriculum
- On to my next adventure
- What to do if you don't get a summer internship
- Monetizing failure: February report
- Accident Prone
- Why I wear a watch
- Monetizing failure: January report
- LoJack solutions
- Getting the most out of your internship
- Favorite Mistakes
2013 56
- Monetizing personal failure
- Special
- Do This
- Top Down and Bottom Up
- Discipline
- Speaking your Mind
- Looking back on a year of blogging
- Starting Well (or, lessons learned from watching Brubaker)
- Pumpkin Nut Bread
- The Curse of the Golden Child
- Mise en place
- Changing your mind, selling out
- Silver Bullets
- Epigrams
- Hackers and Software Engineers
- Things that have outlasted any reasonable expectation
- Hiring - Fast and Slow
- Screwing up
- Politics, self-censorship, and awesome sauce
- Welcome to the team!
- Customer Service
- Why to Write
- The Adults in the Room
- Reading Group: The Power of a Positive No
- Culture Shock: iPhone to Android and Back Again
- Cheating on His Other Love
- Fun vs Satisfaction
- Goal Focus
- Books on Tape
- You Don't Know a Goddamn Thing
- Reading Group: Crucial Conversations
- Letter to a new technical manager
- Mastery
- Intermediate Mastery
- Disaster Movies
- Broke gets fixed, crappy is forever
- Mind Control
- Mastering the Basics
- When Theater is Security
- Lessons from Home: an Interlude
- Anti-Mastery
- How "Senior" Software Engineers are Different
- How to Write a Great Blog Post
- How I know I'm still a nerd
- Opportunityspotting
- Career Management
- Questions I Want to Ask, but Can't
- Staying Technical
- The Cardinal Sin
- Kihon, Kata, and Kumite
- Managing managers
- How to Fail
- Status Reports
- What Do Technical Managers Do, Anyway?
- Message in a Bottle
- Hard Problems
2012 9
- Learn on someone else's dime
- An elegant data type for a more civilized age
- Building a better developer
- How to be a star
- How to prepare for technical interviews
- Why won't anyone talk to me? What recruiters look for in a resume
- Screwing up the technical interview - common mistakes
- Various Approaches to a Simple Interview Problem
- Hello, world
Undated 43
- Filling the interstices
- Monetizing failure march report
- My first big idea
- Monetizing failure april report
- Monetizing failure may report
- Learning from rage
- Monetizing failure june report
- Sticking
- Monetizing failure july report
- Management lessons from summer vacation
- Monetizing failure august report
- Monetizing failure september report
- Feedback
- Monetizing failure october report 2
- Monetizing failure november report
- Faux diy
- Monetizing failure 2014 report
- Hiring technical managers is hard
- Mechanists and humanists across the hiring divide
- Interviewing is hard 2
- Node express reactjs aws a case study in architecture
- Build vs buy
- To infinity and beyond
- The swamp
- Sacred cows and overdue library books
- Shutting down a dream
- The restaurant reviewer
- Working code
- Building a dumber team
- Tools and agents
- The two ai consensuses
- Vibe metrics
- On being in between and ambiguity
- Decisions and will power
- Lost skills
- A taxonomy of trust
- Coding as jazz piano
- How to piss off demoralize and demotivate your team
- How to build a college recruiting pipeline
- Communal responsibility anti pattern
- Old school coding tricks
- Management style
- Seven stages of learning