How to make app fast 1. Profile ✅ 2. Find slowest bit ✅ 3. Make slowest bit faster until it's not the slowest bit ✅ 4. Repeat 1-3 until app is fast 🔁 This is literally the whole process

#TDD is a tool on the toolbelt. Nothing more, nothing less. Sometimes useful, sometimes not. If your team is one of those teams that grills people with a TDD test and gatekeeps non TDD people out of the industry, please stop 🛑

Anyone know a 2-3 month rental in Austin? (preferably near Round Rock.) Starting a new job and not enough room for my wife and me to both work in our condo. Want to live near my parents while figuring out where to move.

Not just UI. APIs Libraries Frameworks Tools Processes ...

💯 I have heard people talking about tests per class, per function and what not. In fact the term "unit" in unit tests refers to a unit of public behavior in my definition. Write tests that verify the algebraic behavior of your model, maybe the domain services. And never write

Dependencies and spaghetti code should be avoided when possible. We don't think about that with CSS, but it's the easiest language to end up with an unmaintainable mess. If you have trouble writing CSS, thinking in terms of dependencies, inheritance, and overriding may help.

I personally wouldn't get rid of version control (and the post wasn't serious). But this is the level of analyzing your processes that I was thinking about. Question EVERYTHING you do. x.com/DevReliefFred/…

Code comments and arch docs often don't include options that were considered but rejected. Valuable work that was lost. Include all the details you have. I consider a commented-out old version of a function to be a useful comment. Especially with a note on why the rewrite.

Stop lying to yourself. Nobody will ever come to you with a perfect specification. Go and ask these questions: 1. What problem are you aiming to solve? 2. Who are the end-users? 3. What are the must-have functionalities? 4. Are there any nice-to-have features? 5. When you

Patterns and libraries are great. But, if you have a complex system/app design an architecture that meets your requirements/needs/roadmap. THEN look for patterns & libs to make implementation easy. Early selection of pattern/lib/framework can hurt design and APIs.

Starting new role at new (to me) company. Was told individual email would be sent to 30+ managers to set up a call with me. Most non-tech. I've worked close with around 5 before. Any advice or differences with 30? (I hope to work with most long term, not a 1 time intro)

Not long ago, 𝗮 𝗹𝗼𝘁 of commodity software dev looked like today's Figma workflows plus basic scripting. The sad irony is very usable software is still WYSIWYG-able, but native UI desktop software is no longer fashionable.

* Collaboration * Coordination * Feedback * Independent work Each individual on the team is best with different amounts (5-95%) of these at different phases of the project. Generic processes don't make your team better. Know the people.

Many tweets that removing code is better than writing code. True. More true for process. Can't remove all code or all process. But that extra meeting, measure, automation, or CI pipeline stage probably isn't improving team output. And may be worse than code technical debt.