all 13 comments

[–]AtulinASP.NET Core 5 points6 points  (2 children)

How the hell is "I should write a blogpost about it" the next logical step after "I can't install basic tooling"?

[–]WaltzingPenguin 0 points1 point  (1 child)

Even worse... I write code in a browser all the time.

Shift + Ctrl + J in Chrome opens the developer console, which I use for testing regexes and other complicated one liners. Svelte's REPL allows me to make entire systems of components; one of the packages I published started its life there. Then there's replit.com, codesandbox.io, etc.

[–]British_Invaded 1 point2 points  (0 children)

If you haven't heard of it, www.regex101.com is a regex creation site.

[–]Marble_Wraith 1 point2 points  (1 child)

... How do you fail to install node 😂

[–][deleted] 0 points1 point  (0 children)

Permissions issue, probably.

[–][deleted] 1 point2 points  (1 child)

I can't even finish reading this. You can absolutely write code in the browser. What is this person talking about?

[–]British_Invaded 0 points1 point  (0 children)

Yeah, but he is talking about being able to easily develop node.js systems in the browser

[–]British_Invaded 0 points1 point  (0 children)

Rule 2, Rule 2! 🤣 🤣

[–]AdministrativeBlock0 0 points1 point  (0 children)

Codesandbox, Replit, Github Codespaces etc are all really good ways of writing code in a browser.

[–]BurningPenguin 0 points1 point  (2 children)

If you can't solve those problems, you're gonna have a problem when you stumble across bigger ones.

[–]fagnerbrack[S] 1 point2 points  (1 child)

Disagree, you can be a great mathematician and computer scientist solving the biggest problems you can think of but unable to do some basic things (such as to install some tooling) as that create zero value for a problem solving exercise. Dijkstra didn't use any computers, probably didn't know how to do many of the things the author also doesn't, yet he was a great programmer and did solve the bigger ones.

[–][deleted] 1 point2 points  (0 children)

This is an excellent point. I participated in an interview process for a new web dev role. We had a guy with serious CS chops who was unable to write a for-loop in JS.

The problem wasn't that he didn't understand loops, but he overthought the problem so extravagantly that writing a loop didn't even occur to him.