Bits
Bits and pieces of software development and Unix wisdom, mixed with some humor.
RSS / Social media: RSS | Mastodon | Bsky
🔗
Threads and signals are a platform-dependant trail of misery, despair, horror and madness.
-- Anthony Baxter
🔗
My definition of an expert in any field is a person who knows enough about what’s really going on to be scared.
-- P. J. Plauger, Computer Language, March 1983
🔗
The Internet was done so well that most people think of it as a natural resource like the Pacific Ocean, rather than something that was man-made. When was the last time a technology with a scale like that was so error-free? The Web, in comparison, is a joke. The Web was done by amateurs.
-- Alan Kay
🔗
When there is no type hierarchy you don't have to manage the type hierarchy.
-- Rob Pike
🔗
Trying to express implicit and fuzzy relationships in ways that are explicit and sharp doesn’t clarify the meaning, it destroys it.
-- Clay Shirky
🔗
An evolving system increases its complexity unless work is done to reduce it.
-- Meir Lehman
🔗
Nobody wants to program with mutable strings anymore, why do you want to program with mutable collections?
-- Rich Hickey
🔗
You want to make your way in the CS field? Simple. Calculate rough time of amnesia (hell, 10 years is plenty, probably 10 months is plenty), go to the dusty archives, dig out something fun, and go for it. It’s worked for many people, and it can work for you.
-- Ron Minnich
🔗
> What does tomorrow's unix look like?
I'm confident that tomorrow's Unix will look like today's Unix, only cruftier.
-- Russ Cox
🔗
Our programming house is like a hoarder's delight: there's too much stuff in it everything is too big. We need too many people to do basic things.
-- Rich Hickey
🔗
The price of reliability is the pursuit of the utmost simplicity. It is a price which the very rich may find hard to pay.
-- Tony Hoare
🔗
The secret to building large apps is never build large apps. Break your applications into small pieces. Then, assemble those testable, bite-sized pieces into your big application.
-- Justin Meyer
🔗
Increasingly, people seem to interpret complexity as sophistication, which is baffling - the incomprehensible should cause suspicion, not admiration. Possibly this results from the mistaken belief that using a mysterious device confers [extra] power on the user.
-- Niklaus Wirth
🔗
Theory and practice sometimes clash. And when that happens, theory loses. Every single time.
-- Linus Torvalds
🔗
Be careful to preserve the orthogonality of your system as you introduce third-party toolkits and libraries. Choose your technologies wisely.
-- Andy Hunt
🔗
That's what's cool about working with computers. They don't argue, they remember everything, and they don't drink all your beer.
-- Paul Leary
🔗
A generalist is a jack-of-all-trades but a master of none, whereas a generalizing specialist is a jack-of-all-trades and master of a few. Big difference.
-- Scott Ambler
🔗
So much complexity in software comes from trying to make one thing do two things.
-- Ryan Singer
🔗
The lurking suspicion that something could be simplified is the world's richest source of rewarding challenges.
-- Edsger W. Dijkstra
🔗
Premature optimizations can be troublesome to revert, but premature generalizations are often near impossible.
-- Emil Persson
🔗
Compatibility means deliberately repeating other people’s mistakes.
-- David Wheeler
🔗
The cost of adding a feature isn’t just the time it takes to code it. The cost also includes the addition of an obstacle to future expansion. […] The trick is to pick the features that don’t fight each other.
-- John Carmack
🔗
The first rule of functions is that they should be small. The second rule of functions is that they should be smaller than that.
-- Robert C. Martin
🔗
It can be better to copy a little code than to pull in a big library for one function. Dependency hygiene trumps code reuse.
-- Rob Pike
🔗
The standard rule is, when you're in a hole, stop digging; that seems not to apply [to] software nowadays.
-- Ron Minnich
🔗
It should be noted that no ethically-trained software engineer would ever consent to write a DestroyBaghdad procedure. Basic professional ethics would instead require him to write a DestroyCity procedure, to which Baghdad could be given as a parameter.
-- Nathaniel Borenstein
🔗
The code you write makes you a programmer. The code you delete makes you a good one. The code you don't have to write makes you a great one.
-- Mario Fusco
🔗
We build systems like the Wright brothers built airplanes - build the whole thing, push it off the cliff, let it crash, and start over again.
-- Nato Software Engineering Conference '68
🔗
I love deadlines. I like the whooshing sound they make as they fly by.
-- Douglas Adams
🔗
Good code is its own best documentation. As you're about to add a comment, ask yourself, "How can I improve the code so that this comment isn't needed?"
-- Steve McConnell
🔗
If you are choosing a JavaScript library purely based on popularity, I think you deserve what you get.
-- Tom Dale
🔗
I am rarely happier than when spending entire day programming my computer to perform automatically a task that it would otherwise take me a good ten seconds to do by hand.
-- Douglas Adams
🔗
Hiring bad developers is like drinking seawater. It seems to satisfy a need while actually increasing it.
-- Michael Nygard
🔗
Functions should do one thing. They should do it well. They should do it only.
-- Robert C. Martin
🔗
If it doesn't work, it doesn't matter how fast it doesn't work.
-- Ravera's observation on premature optimization
🔗
If you want to confuse your enemies, give them the source code. If you want to really confuse them, give them the documentation.
🔗
Any intelligent fool can make things bigger, more complex, and more violent. It takes a touch of genius - and a lot of courage to move in the opposite direction.
-- E. F. Schumacher, Small is Beautiful