Software Architect – A Role, Not a Job
A structure where software architects work on a team separate from the development team can lead to dysfunction, reduced quality, and poor morale.
Every blog post that took off on Hacker News, ranked by the votes of its best submission. 6,087 posts.
A structure where software architects work on a team separate from the development team can lead to dysfunction, reduced quality, and poor morale.
Molly Graham helped forge a work culture at Facebook that's withstood huge amounts of growth. Today, she's something of a rapid scaling expert. Here's the key to doing it right, she says.
In his book On War, Clausewitz defines friction as the difference between military theory and reality: Thus, then, in strategy everything is very simple, but not on that account very easy. Everything is very simple in war, but the simplest thing is difficult. These difficulties accumulate and produce a friction, which…
As part of the same process outlined in Matthias Clasen's "LibreOffice packages" email , my management chain has made the decision to stop a...
Junior developer (for purposes of this post)is a developer with < 2 years experience programming in industry who have an interest in sharpening their technical skills. I recently graduated from Stanford with a degree in Computer Science. I’ve been programming for 4 years and feel comfortable claiming ~1.5 years…
For the past several years, I’ve run a learning circle with engineering executives. The most frequent topic that comes up is career management–what should I do next? The second most frequent topic is measuring engineering teams and organizations–my CEO has asked me to report monthly engineering metrics, what should I…
Some people believe that carrying out a large software project is like building a bridge. You look at your past projects and use the data to estimate the time and resources needed. This view has been debunked decades ago; this analogy was frequently seen as an aspiration for the future when I did my Master in Software…
We need your experiments and your questions and your feedback. Your lack of understanding is a valuable attribute that goes away as you gain experience.
How should you structure a larger engineering organization, one with dozens (or hundreds) of engineers? There are many tradeoffs to consider, and no single right answer. But, there are some structures that work better than others.
Introducing new web service to determine if a number is odd or not. No new code dependency in your npm modules. Can use with almost any programming language, not just Javascript under node.js. No license. Easy to test in a web browser
The guilt can be crushing. Everyone seems to be getting stuff done, except you. ...
How to close patches for your open source project you don't want.
We help you acquire the perfect domain for your site. Affordable payment options. Quick and responsive customer support available.
My story so far!
Personal writing by Walid Dib, and a collection of games, apps, and companies I’ve built.
You should be multi-faceted, never work purely to your technical abilities, think about how you can make your entire company better
Over the course of my career, I've found two characteristics to be among the most important for software developers to thrive.
I'm used to getting asked how many employees work at my startup. For most people, it's a quick way to assess a startup's success. Supposedly, the bigger, the better. But does it really reflect success?