Xen0byte

If I "walk along the train while riding it", as the author suggests, I can get from any station to any other station. Taking the tube from Moorgate to Barbican is not the same thing as walking underground, so this article is somewhat misleading.

I would strongly argue against this. Not only TODO is easily searchable as others have also pointed out, but also in some IDEs you can open a TODOs window which will aggregate all of these so that you can easily keep track of them (e.g. Visual Studio).

I recently went through the same process for a director of engineering position and it was OK up to the point where a VP thought that asking me low-level detail questions specific to his particular project which I had zero knowledge of was the appropriate way of assessing the potential of a candidate applying for a position spanning the company's entire product portfolio; needless to say, I didn't do that great. The peer-review stage is a tricky one because if a single person on one of the 12-ish interviews doesn't like you then that's the end of it, and you might have the luck of running into some uninspiring automaton with a military background like I did.

OP follows Andrew Huberman. https://www.youtube.com/watch?v=8IWDAqodDas :)

I dislike emails that end in "Thank You In Advance" with such a passion. It's so presumptiout to assume that I will agree to whatever the request is; OK, I might, but don't thank me for something I haven't yet agreed to do, you're just implying that I have no option but to agree. These emails have the lowest reply rate in my mailbox.

I'm very curious to find out how it compares to Playwright.

While I normally argue in the favour of privacy, in this particular case I'm leaning towards thinking that web content accountability is a step in the right direction.

Firstly, I stopped taking this article seriously at "modern language (Java)". Apart from that, "we can decide to not put bugs in the code" is the most non-sensical thing I've ever read. OK, sure, you can eventually flush some or most bugs out before your code goes in for proper testing from formally-trained QA people, but unless all you're writing is "Hello World" applications or walking skeletons then writing bug-free code is not possible, hence the existance of an entire industry that revolves around finding bugs. Just because YOU can't find any more bugs in your own code, that doesn't mean there aren't any bugs in the code, which is why QA people are trained to employ methodical test techniques. This is commonly known as the "Absence-Of-Errors Fallacy".

Secondly, there's this concept called "Independence Of Testing", which essentially states that the more independent the tester is from the code, the more likely they are to find defects. The opposite of that is also true, the less independend the tester is, e.g. if the tester is the developer, then the less likely they are to find defects in their own code. Read mode here (section 5.1.1): https://www.istqb.org/downloads/send/2-foundation-level-docu...

Lastly, this article is essentially saying that proper testing by QA people is useless, which not only I strongly disagree with but also is something that a terrible developer would say.

I've just given this a try, and it's a fantastic bit of software. I'll definitely be switching over to it.

Very good counter-argument to the non-sensical punctuation mark redundancy argument.

Exactly, both approaches in the article are wrong, and this is the only way to write the sentence correctly. Each sentence needs to end in a punctuation mark, regardless of whether it's between quotes or not.

I don't agree that a transformation which takes an int[] and outputs a string[] is an endofunctor. Yes they are both arrays, but they are different types.

I put that in the original title, but I think it got edited out by a mod. :)

Hi, just to chip in because I read your request for feedback and also because I'm interested in seeing what Monito can do. I’ve been heading QA depts at large tech companies for a while now, and part of my job is to be up to speed with the latest tools and trends, and to write automation tools for various tech stack layers. To answer your question, my preferred front-end tool at the moment is Playwright (via C# binding). Playwright is the new kid on the block, but it has great potential; I’ve migrated all of our Selenium tests to it and I couldn’t be happier.