Trip C++Now 2024 – think-cell

I&#x27;ll say this because it needs to be said. Recently it seems like every developer on LinkedIn who has &quot;C++&quot; in their profile, and their cat, is spammed every couple of weeks by some recruiter with a &quot;great opportunity, 130,000 euros FULLY REMOTE&quot;, turning out eventually to be recruiting for think-cell.<p>I got it, my friends got it, my work mates got it, everyone gets spammed periodically, it has become the laughingstock of job ads.<p>Why? Read the Glassdoor reviews. The CTO is a terrorist obsessed with complexity, they overengineered themselves into a corner by using every freaking C++ feature that ever existed, making sure that there&#x27;s only 3 or 4 people in this world who can understand their code. Of course the usual pattern goes: guy learns #feature on-the-fly appearing both incredibly smart and embelishing his resume, until of course reality hits and the complexity of the crap he wrote outclasses his &quot;genius&quot; intellectual capacity so then he leaves, leaving the mess for future hires to deal with.<p>Consequently there&#x27;s maybe 3 people left in this world capable to understand the atrocity that&#x27;s running there, not saying fix it. So good luck finding them. These people, if they exist, already work for more that $130k.<p>Also, why do they need the absolute raging brinking edge of C++ features? What does this company do? Trillion dollar ultra low latency &#x2F; high throughput high frequency trading? AAA+ games running on 4 x 4k monitors at 200+ fps?<p>No. They do some farty charts.<p>Again. Good luck with the recruitment! :)

&gt; Google does not use std::ranges for many reasons, including performance, the ability to create dangling references, and a cubic stack blowup when deeply nesting some range adapters like std::views::filter<p>I remember discussing this exact problem for boost range in the boost mailing list almost 20 years ago. My proposal was to make ranges be their own thing and generate the iterators on the fly when begin&#x2F;end was requested, instead of always storing them internally. But I think it was not considered a big issue in practice.<p>Today we have sentinel end-iterators that can be stateless, so it should be possible to avoid blowout without fundamentally rethinking ranges.

Did their 4-9 hour(!) mandatory take home coding test. Never done such a terrible test in my life; in every way they made a test akin to basically locking a c++ dev in a room for anywhere between 4-9 hours and afterwards rolling a die.<p>Its underspecified, but then has automated tests, that, after failing twice, automatically reject you as a candidate. Of course it doesnt give examples or example test cases or real test cases, so you&#x27;re shit outta luck trying to solve it. The challenge itself would be fun and solvable in 4 hours, but around the 2 hour mark you start having questions and from there its just bad.<p>You can google this coding test (&quot;think-cell interval_map&quot;) and youll get a lot more info.<p>I complained to them just in case they cared, and they did seem to care, but failing to specify an automatically tested coding challenge is the kind of psycho shit you do if you think youre the smartest guy in the room (but arent).<p>ETA: To be clear, I stopped the second I realized it was an underspecified test. I&#x27;m not that mad, just mad I fell for spending a whole saturday morning doing it, without ever talking to anyone there in a call or anything.<p>That and the fact that theyre just building a powerpoint plugin and seem to overcomplicate it to such a massive degree: Yeah no thanks.

Rappel sounds very similar to Clojure’s transducers in spirit and implementation.

Regarding the addition to libxx: I’m not fond of adding an increasing number of specific compiler options which need to be turned on for memory-safety. It should be default whenever possible. What do you think?<p>I love <i>-faddress=sanitizer</i> or <i>-fsanitize</i>. The historically growing number of warnings which should be turned on are an issue. For example the options -Wconversion, -Wsign-conversion and -Warith-conversion shall be default with <i>C++XX</i>. And if your code doesn’t compile, fix it, use and older revision or turn it deliberately off (saying: I’m aware, read the handbook, I take the risk). Doing such changes with language revisions allows people to take notice about it without surprise.<p>I want some ideas of CPP2&#x2F;cppfront[1] in C++XX. Finally using <i>#unsafe</i> when needed, like Rust. C++ does evolve over decades, more like other languages.<p>[1] <a href="https:&#x2F;&#x2F;github.com&#x2F;hsutter&#x2F;cppfront">https:&#x2F;&#x2F;github.com&#x2F;hsutter&#x2F;cppfront</a><p>BTW. Use the AddressSanitizer. Please! The toolchain improved the usage and safety of the language so much. It wasn’t available twenty years ago but it is now.

I created a similar sum type during high school detention but type order didn&#x27;t seem possible at the time. I&#x27;m glad someone else has eyes on it.<p>I unfortunately don&#x27;t write C++ anymore because the TC is too low. It&#x27;s sad that Python and JS pay more.

Think cell is the company the creator of lexy works at