“[Younger programmers] might insist that everything is new and different nowadays, that the rules of the past are past and gone. If that is what they think, they are sadly mistaken. The rules have not changed. Despite all the new languages, and all the new frameworks, and all the paradigms, the rules are the same now as they were when Alan Turing wrote the first machine code in 1946. But one thing has changed: Back then, we didn’t know what the rules were.”


"Before you begin anything else, summarize your ideas in an issue and share it. It’s such a simple rule, but the impact is huge."

A system’s being “fail-safe” means not that failure is impossible or improbable, but rather that the system’s design prevents or mitigates unsafe consequences of the system’s failure. That is, if and when a “fail-safe” system “fails”, it is “safe” or at least no less safe than when it was operating correctly.

"We don't need competition between people.
There is competition between every person and this mountain.
The last word always belongs to the mountain."

> We could, for instance, begin with cleaning up our language by no longer calling a bug a bug but by calling it an error. It is much more honest because it squarely put the blame where it belongs, viz. with the programmer who made the error.

"By bootstrapping your app with a fully coded mobile app template, you can save months of development and tens of thousands of dollars."

> flip.it/S-pci4

"When you're a "maker" instead of a manager, you are focused on your individual projects and tasks. When you enter into a leadership role, those things are no longer your priority. You. Must. Let. Go."

Show more

rtHome Socials