234 karma · joined December 12, 2019
Ideally people would just be polite, and questions could just be answered by anyone who cared to answer them, with low-scoring exchanges de-emphasized instead of being shut down.
Building an executive oasis in the office probably counts as some kind of warning sign. Departure from reality.
If "category killer" is a winner-take-all competition, then there are going to be a vast number of losers, and we do see a vast number of unmaintained projects. It's just that no one is bothering to remove them from view when they're defeated.
If your side-project has a low probability of a high reward, then having a steady paycheck from a job is a good floor to have under you, if you're not floating around on a cushion of wealth. The author closes with "I hope you have what it takes to commit and become a real entrepreneur" but the reality is "what it takes" is to a large extent money. If you don't have it, you need to get it from your day job.
But trying to get more effort for the same money by anathematizing side projects breaks encapsulation on the employee/employer relationship. It's obnoxious and involves matters that are (literally) none of his business (at least in California).
Those tools are relegated to a small section at the end, whereas the main body of the text says "Pipenv is recommended for collaborative projects..."
I'd say that counts as a specific endorsement of Pipenv. I guess it's an endorsement by the "Python Packaging Authority" rather than "Python Core" but it's pretty hard for someone at the tutorial-reading level to perceive the difference.
Node is a gateway to Javascript fluency for people that get a headache dealing with the DOM in the browser. You can write command-line scripts, run them with "node [scriptname]", and learn.
Having done that, I've found that Node is great for fast prototyping of servers, even if those are going to be written in C/C++ ultimately. In not-super-formal work environment, you can very quickly write something that runs with the correct behavior, and treat that as the spec for the final performant code.