Found 46 bookmarks
Custom sorting
Don't Do This in Production
Don't Do This in Production
Around March of 2017, I received a call asking for a code review on a product about to be launched. This company had issues with memory leaks, spontaneous crashing, slow loading, CPU spiking, and had to release in a couple of weeks. You might have heard this story before, just not from me, and not about this company. It’s surprisingly common. We got together on the weekend and started looking through the code together.
·stephenmann.io·
Don't Do This in Production
bliki: Yagni
bliki: Yagni
Yagni ("You Aren't Gonna Need It") is the principle that we should not build presumptive features. It should not be used as a justification for neglecting internal quality.
·martinfowler.com·
bliki: Yagni
Things You Should Never Do, Part I
Things You Should Never Do, Part I
Netscape 6.0 is finally going into its first public beta. There never was a version 5.0. The last major release, version 4.0, was released almost three years ago. Three years is an awfully long tim…
·joelonsoftware.com·
Things You Should Never Do, Part I
5 Red Flags Signaling Your Rebuild Will Fail
5 Red Flags Signaling Your Rebuild Will Fail
There’s always a reason to rebuild. Perhaps you’re a CEO of a startup that’s had some success and your engineers are clamoring to replatform and do a rewrite from scratch. Perhaps you’re an executive or IT lead and you’re counting the cost of pulling the trigger on a rewrite of a legacy application. Perhaps you’re a lead engineer in the midst of a rebuild and are having second thoughts (am I crazy?). Regardless of where you’re at, you likely already know that talk of rebuilds, like talk of tax reform or anarchy, is just a tad bit dangerous—you never know what kind of danger you’ll end up in...
·pkc.io·
5 Red Flags Signaling Your Rebuild Will Fail
Simple, correct, fast: in that order
Simple, correct, fast: in that order
The single most important quality in a piece of software is simplicity. It’s more important than doing the task you set out to achieve. It’s more important than performance. The reason is straightforward: if your solution is not simple, it will not be correct or fast.
·drewdevault.com·
Simple, correct, fast: in that order
It doesn't have to be crazy at work
It doesn't have to be crazy at work
Trusted by millions, Basecamp puts everything you need to get work done in one place. It’s the calm, organized way to manage projects, work with clients, and communicate company-wide.
·basecamp.com·
It doesn't have to be crazy at work
Software Complexity Is Killing Us - Simple Thread
Software Complexity Is Killing Us - Simple Thread
Since the dawn of time (before software, there was only darkness), there has been one constant: businesses want to build software cheaper and faster. It is certainly an understandable and laudable goal – especially if you’ve spent any time around software developers. It is a goal that every engineer should support wholeheartedly, and we should... Read more »
·simplethread.com·
Software Complexity Is Killing Us - Simple Thread
The Art of War by Sun Tzu
The Art of War by Sun Tzu
The Art of War has 222,853 ratings and 6,925 reviews. Anne said: Hey! Look at me stepping outside my comfort zone!I saw this audiobook in the library...
·goodreads.com·
The Art of War by Sun Tzu
The Joel Test: 12 Steps to Better Code
The Joel Test: 12 Steps to Better Code
Have you ever heard of SEMA? It’s a fairly esoteric system for measuring how good a software team is. No, wait! Don’t follow that link! It will take you about six years just to understa…
·joelonsoftware.com·
The Joel Test: 12 Steps to Better Code