That specific question is not great for this purpose.
4o model with web search enabled: "As of May 2025, there is no ISO 9002:2023 standard. The ISO 9002 standard was officially withdrawn in 2000 when the ISO 9000 family underwent significant restructuring. Since then, ISO 9001 has been the primary standard for quality management systems (QMS), encompassing the requirements previously covered by ISO 9002."
Indeed the more advanced ones catch this particular one. I could trick phind with
"Explain the IEEE 1588-2019 amendments 1588g and i impact on clock synchronization" (g exists, i does not but Phind hallucinates stuff about it). Perplexity catches it, though.
The recipe is the same, you just have to try several models if you want to get something that gets many engines to hallucinate. Of course nothing is _guaranteed_ to work.
I used to own a Fold 4 and it's a wonderful device, I really loved it (mostly the multitasking, stylus support, small outer screen for one-handed use). Unfortunately, the design is truly fragile and I sold mine after I got it back from the repair shop for the second time (and got a boring iPhone). I truly hope newer generations will be better and I can purchase one that will last at least 3-4 years.
Yep that one! It's a bit pricy for 'private' people (I think 300 or 400?) for what you get, it's essentially a bunch of statements you click on as fast as possible, and then you get a PDF with a final report. If your employer pays for it, go for it. I think it has helped our management a bit with shaping team 'even-ness' - some teams should be good mixes of all strengths, not just 100% 'input' as you get in regular data teams.
I've got a CS related degree, but I'm a mostly self-taught dev, and not understanding 90% of the code really makes me reevaluate my career choices. Where and how can I learn this stuff?
Do you want to learn it because it looks interesting, or because you think it's important for a Real Programmer to know?
If it's the former, go for it.
If it's the latter, don't worry about it. I have a CS degree, did 6 years on a team writing C++ at Microsoft, and only briefly flirted with understanding this stuff. A couple of the wizard devs on the (very large) team could do it, but they also knew that code needed to be simple above all else, so it was effectively banned in our code base.
There are 2 components here. One is the "type metaprogramming" - (mis)use of the type system to implement to do compile-time computation, mainly by using parametrized types as kinda-functions + type inference for kinda-pattern-matching.
The other is building up basic "data types" by pretty standard lambda calculus > LISP route.
"Understanding Computation" book has a great chapter 6 on that, which is available in blog & video forms on https://computationbook.com/extras
- Here, Church numerals were used to represent numbers.
- booleans & conditionals here didn't resort to the lambda representation you'll see in the book, but relied on type conditionals builtin to TypeScript.
- The names "Cons" & "nil" are a ringer for LISP-like building of lists, and recursive processing of lists, from a "pair" data type.
Sorry, i misspoke about "Church numerals". The book uses them to represent non-negative integers by lambdas but here that wasn't necessary, TypeScript allowed a simpler representation of N as a the type of an N-deep nested list.
What's common to both approaches to building arithmetic is starting from zero + a "successor" function T. That approach is called "Peano arithmetic".
I still recommend that post/video (and the book in general) but I have to admit there is no 1:1 correspondence to the TypeScript going on here.
Still, it'll teach you some general maneuvers for bootstrapping computation out of almost nothing , qnd once you're comfortable with those, you can read things like this TypeScript post, or aphyr's original Haskell post, which bootstrap computation out of sjighly different" almost nothings" and without following the details still have a high-level idea of where it's going (like the poor interviewer in the story ;-)
Yes it's mostly because it looks interesting and fun. I definitely agree these type-golf-esque solutions are not ideal in an enterprise project especially where we have juniors and fullstack devs committing a lot of FE code.
Don't worry. I assure you that many senior devs can't follow this article either without some further digging. This is a puzzle interview task, not something that matters in most peoples daily work.
Not the OP. I understand my situation might be a bit specific, but I'm a single guy living in a small apartment in his very early 30s with not a lot of friends and family (important point that my commute to the office is a 15 minute walk). We basically have an unlimited WFH policy, but I still like to spend at least 2-3 days in the office as I've noticed it has some strong benefits. There might not be exactly 10 of them, but for me it's definitely enough.
- It's something that makes me leave the house
- I've found that being around people has a positive effect on my mental health and general wellbeing
- As I live in a small apartment, I don't have the desk space for a multi monitor setup I would prefer
- The coffee is just way better than the one I am able to make at home
- It's an occasion when I have to look presentable, so I'm taking better care of myself
So going forward, we need to realize people are in different situations, situations can change and if the employers care about their employees the WFH option needs to stay.
tl;dr: It knows