mxz3000

From my (probably naive) point of view this does seem like a useful feature for users. If you can get an accurate answer for your query without clicking on a link or having to grep the linked page for the answer that's a win in my book and a time save for users. I guess an issue arises when the snippet is _not_ correct. But in my personal experience, the snippets are usually pretty helpful/accurate

At least in engineering, there's quite a lot of autonomy. Senior leaders set the overall vision/objective, but in the end it is up the engineers and product managers to figure out what actually to work on.

Cdk is the way to go for pretty much anything. It's so much faster to develop an infrastructure in cdk than it is in cloudformation it's insane

My experience has been similar to yours. The company I work at has very complex business logic written as a custom DSL parsed/executed by a crazy pile of Perl code.

Recently we had requirements to come up with a way of providing on-the-fly validation in a web editor. This was only possible by ditching the old implementation and re-writing the grammar using ANTLR. While the old implementation is unmaintainable and (probably, who knows?) buggy, the ANTLR implementation is trivial to work on, test and add new features to.

If you're working with a limited time budget, which is common when your main job isn't to maintain the language, then parser generators such as ANTLR are a godsend. ANTLR even enables you to generate parsers in different languages depending on where it needs to be executed. Need something to run client-side, in the users browser? Generate a JavaScript parser and you're done. Need it to run in the Java backend? Generate it in Java and call it a day.

While it's true that error handling isn't the best, it's already better than nothing, and, as you say, can probably be improved with a bit of customization.

It's ridiculous anyone should have to think about this at all. I'm happy to be European right about now.

Same here. It's brilliant. The type system is so good that it's painful when you have to go back to writing Java (for the backends) and it's substantially inferior/archaic type system. Going to back to legacy UIs that use old school JavaScript is similarly painful...

I have to disagree. Unit testing comes as soon as you write _any_ code. You write a new function/class? Your pull request better have unit tests for it or I'm rejecting that shit.

Yup I used bit sets to write a super duper fast Sudoku solver. For examples you can detect naked singles extremely fast by just and-ing the bitsets in a given row, column or house, taking the complement, and checking if a unique bit is set.

Sure when you're the only one working on a project. Otherwise, the only right way of writing code is that agreed upon by the whole team. Any personal opinion, while affecting the 'opinion' of the team, does not matter.

Oh that explains everything. That's what I get for being too lazy and not reading the fine print I feel happy now at the fact that my solver is about 2 orders of magnitude faster than his!

Sure. My solver is designed to return the first solution it finds (it doesn't check for solution uniqueness, just that there is one). However currently my solver is saying that it can't find _any_ solution at all.

Hmm it's weird. I tried my solver on it and it tells me that it can't find a solution (in 13 seconds). My solver is pretty well tested (on some very difficult sudokus as well). Maybe this guy's solver is bugged?