361
That won't scale: Present cost vs. future value
Thanks for reading Code Solo!
362
How to find your blind spots
You probably aren't qualified to dissect your own failures because you're the idiot who screwed everything up.
363
Stéphane Graber has left Canonical
Stéphane Graber's website -
364
Coaching engineering managers to take on organizational problems
In an organization with many teams, problems will arise that span across these teams and require solutions broader than an individual manager’s purview. These types of projects include things…
365
YOLO-Driven Development Manifesto
YOLO-driven development - not for the faint of heart
366
Story Behind Hackathon Photo
How a random stream of events ended up creating a picture with 57 million views
367
368
The Risks of Staying Put
Friends! Pals! Treasured work associates! Last month Mandy Brown wrote about how she struggled to quit her job and this bit hit me like a sledgehammer: “I...
369
What’s the point of tech conferences?
It’s con season in the tech world. Yesterday evening I flew from Pluralsight’s Link/ unconference in New Orleans to Pycon US in Salt Lake City. New Orleanians are just as likely as not …
370
Communication as a critical business skill
There is more to communication than just the correct use of words, phrases, and clauses. Let’s look at some of the communication skills that don’t get enough attention.
371
Reflections on My Decade at Sumo Logic
Debug, simplify and execute.
372
Earning the privilege to work on unoriginal problems
The startup world is almost by definition a place where you “live in the future”. Working in an early-stage startup, your whole belief system is based on being able to successfully create something new. Something that will become a great and cherished product, used all around the world. It needs to be this way, or…
373
Limits of Programmer Productivity: A lesson from Fred Brooks
Fred Brooks published The Mythical Man-Month in 1974, describing the lessons he learned leading IBM’s OS/360 project during the 1960s. As technology goes, it’s ancient. Consider the workflow for a “debugging run”:
374
Why you’re going about recovering from perfectionism all wrong (2021)
Stop murdering your village of weirdos.
375
The ARM powered ThinkPad x13s, as a developer
The ARM powered Thinkpad x13s is the first truly premium Windows on ARM laptop. Let's see how that actually stacks up as a software engineer!
376
Looming demise of the 10x developer – an era of enthusiast programmers is ending
Justin Searls on the looming demise of the 10x developer: Why an era of enthusiast programmers is coming to an end.
377
Cognitive distortions that undermine clear thinking
Leaders are paid to think clearly. And a big impediment to clear thinking is what CBT/REBT calls Cognitive Distortions: errors in thinking or thinking traps we commonly fall for. Most high-performers are not pathological, but instead fall for them when upset or in high-stress situations. In this
378
Development slowness in big and legacy applications
Software companies come in many sizes. There are small startups, medium-sized companies, and huge enterprises. As you might expect, startups are usually lean and fast. Big companies that develop large applications move much more slowly. Those might be systems developed for many years or decades by hundreds of…
379
How to add documentation to your product life cycle
An evaluation of different processes used to create documentation, and their advantages and disadvantages for the organization, the customer, and the writer.
380
Mistakes You Should Never Make (2014)
I was walking to a team meeting where I was going to announce that we would likely have to lay off nearly all of our employees because we unexpectedly had almost no money left, and that it was all my fault.
381
Making OKRs more playful using hill charts
OKRs for Managers and C-Level? Great! But have you ever asked your teams? In this post I am sharing how I make OKRs less dry and more enjoyable for the teams I manage.
382
383
How (not) to apply for a software job
Advice for how to (and how not to) apply for a software engineering job, particularly for the written parts of the interview process. As a bonus, some tips for your resume/CV.
384
Winner’s Curse: Negotiation Mistakes to Avoid
Imagine that at the beginning of class, a professor produces a jar full of coins and announces that he is auctioning it off. Students can write down a bid, he explains, and the highest bidder wins the contents of the jar in exchange for his or her bid.
385
Building big systems with remote hardware teams
The product we’re building, a rack-scale computer, is specifically designed to be a centralized, integrated product because that’s what our customers need. This requirement and the design choices we’ve made to meet this need create some daily efficiency challenges for our team. As a remote-first company, we’re…
386
Stefan Tilkov has died
INNOQ Deutschland mourns the loss of its co-founder and CEO, Stefan Tilkov
387
Demystifying burnout – A deep dive into its symptoms and remedies
Discover the roots of burnout, its distinct symptoms, and key causes. Learn to identify potential signs and explore strategies to overcome this chronic syndrome.
388
Docs Deserve More Respect
A plea for more respect for documentation and technical writing in the software development industry.
389
Street fighting engineers vs. martial arts engineers
Street fighters and Martial artists.
390
Building personal and organizational prestige
Most months I get at least one email from an engineering leader who believes they’d be a candidate for significantly more desirable roles if their personal brand were just better known. Similarly, when funding is readily available during periods of tech industry expansion, many companies believe they are principally…