I just peeked at the docs and right off the bat I don’t like how they have conflicting attributes like hx-get and hx-post. What happens if both are set at the same time? Why not just have hx-method?
I just peeked at the docs and right off the bat I don’t like how they have conflicting attributes like hx-get and hx-post. What happens if both are set at the same time? Why not just have hx-method?
By the end of the meeting you have 10 more questions and no answers and more meetings to discuss the new questions
I try and follow best practices always too, but when the linter is catching it for you it’s less to think about so you can focus on the important parts of the problem
Typescript compiler enforces language requirements, the linter enforces language best practices. Best practices help you avoid bugs.
Same reason you use typescript. It helps you catch bugs and follow programming best practices. You also don’t need typescript, but with it your code is better. Typescript is technically just a really fancy linter. The actual compilation mainly just removes the type data and does some JavaScript engine compatibility.
Why do the typescript extensions to eslint exist then?
And eslint and setting up tsconfig for your project structure.
They probably spent a year looking for a job and they’re suffering from imposter syndrome so they feel like if they aren’t constantly getting stuff done they might be fired, plus they haven’t worked enough to hit burnout and don’t know how to pace themselves.
Maybe there’s some edge case but in my years of using prettier I haven’t encountered one once.
It adds even more auto formatting rules so you can basically stop thinking about formatting entirely. I used to be opinionated about formatting but now I just go with whatever prettier does. It’s not always the best but it’s consistent and it’s a big chunk of my brain I can free up for things that matter. It also formats things safely so you don’t run into those weird edge cases where semicolons matter if you choose to turn them off.
I’ll add that to my mountain of reasons for using typescript
After switching to typescript with linting and prettier I simply hate writing vanilla JavaScript anymore. Some people complain about the extra project setup needed but I find that time pays for itself immediately.
I wouldn’t do it without an auto formatter. With prettier it will catch potential no semi colon issues.
I’ve seen this argument so many times and it makes zero sense to me. I don’t think by predicting the next word, I think by imagining things both physical and metaphysical, basically running a world simulation in my head. I don’t think “I just said predicting, what’s the next likely word to come after it”. That’s not even remotely similar to how I think at all.
Depends on your definition of AI, and everyone’s definition is different.
Push and pull are purposefully similar because they’re doing the same actions in opposite directions
I think a lot of academic oop adds inheritance for the heck of it. Like they’re more interested in creating a tree of life for programming than they are in creating a maintainable understandable program.
Advice on what instances to join, coordination to move communities, technical advice for those communities to form instance, etc.
Why was this written like this? It makes no sense. I’ll git blame it and ask them what’s going on. Oh it’s me…