beryilma

The color contrast of the site, especially the background color and the font thickness (on android phone at least) is not good. Many visually impaired people would have very difficult time reading the content.

> Sold out, please go back and pick another option.

Funny how a "free" PDF book can be sold out.

As much as I appreciate the author's effort, if I have to enter my email to get the "free" book, then the book is not free.

One might even argue that a Turing Machine (computers) is really one dimensional.

This is 5 times more readable than FP example above for the same computation. The FP example uses variable book(s) five times, where using it once was sufficient for SQL. Perhaps FP languages could have learned something from SQL...

Github, nodejs, and PM2.

I can deploy to my local machine AND to EC2 with a single deploy command using PM2 configuration facilities. This works quite well for side projects.

I also have nginx and postges running on both locations with local (to the server) database connections without opening unnecessary ports to the world.

> Lately, I've built simple websites and small web apps in vanilla Javascript and CSS

Any public links?

a.k.a. Emacs.

Out of curiosity, what level of $ amount are you talking about?

> but I started to realize that pushing 50 and being as cynical as I now am, I'm pretty much unemployable as an IC.

Well that's me. My theory is that it is not age that makes one unemployable in the software industry, but the unwillingness to put up with shit cooked up by bunch of 25 year old CEOs, CTOs, and the like.

"Uncle Bob" is not a software engineer (as he calls himself) and anything he says on the subject is theoretical at best, and snake oil at worst. Can anyone point to any substantial piece of code that he wrote before he can be taken seriously. The code pieces at his GitHub repos, other than style, etc., are just simplistic stuff.

It is probably OK to be thinking on issues related to a field (i.e., software engineering) without being a practitioner in the field, but producing fads-du-jour and selling them as solid (pun intended) theories and expecting to be taken seriously is just ludicrous to me.

The problem with software estimation is that the requirements change constantly because customers often don't know what they want until they see a prototype or a mock of the system. Then, you constantly get unspecified, subtle requirements in endless emails starting with "I would also like to ...", without the customer realizing what they are asking for and how that might effect the deadlines.

> People who stress over code style, linting rules, or other minutia remain insane weirdos to me.

Until you open a file that has 10 different coding styles from 5 different developers. Just the variations of variable naming schemes alone in individual code files that I see/edit, would drive anyone crazy.

> Yes, you guessed it, let's go with Electron and CoffeeScript.

> The main tech stack is still CoffeeScript, but we changed the UI framework from React to Riot.js.

> I've installed Babel, Mocha, ESLint, and added libraries via npm.

> I've rewritten my entire code base from CoffeeScript to ES6.

> The introduction of MobX, a state management library, and the introduction of Flow, a type checking system.

> So I rewrote everything in TypeScript, including my own libraries.

> Anyway, I'll be replacing my own components like Button and Toolbar with Material-UI ones.

> It's time to rewrite everything to styled-components.

> It's time to rewrite everything to useXXX.

No wonder why these software projects (personal as well as professional ones) are 6 years late. It may be a good learning experience, but a terribly inefficient way of developing software.