W0lf

That sounds a lot like the idea from Peter Huth’s Mail-Terror-Blocker PRO, a theater drama studied guy that happened to become an _internet expert_ by accident here in Germany back in the 2000s. Unfortunately, his program failed in the most hilarious ways and quickly became a joke in the usenet groups back in the day.

An opinionated thorough demonstration on how to write C++ at scale. I didn’t agree one all aspects, though I have to admit it was the first book on C++ that clearly stated _how_ to actually design stuff both on a physical as well as on a logical level. Something which most other books on C++ won’t get into. All that being said I think it was pretty relevant for medium to large codebases

Given that I am working professionally with C++ (meaning I earn money by writing code in this language) I find it remarkable, that I appreciate and actually think it’s a useful book for my daily work. 1300+ pages of detailed language features just to somewhat get by and feel sufficient competent that my code does what I intended to do.

Looking behind my back there is a shelf of another 30+ books full of C++ (Meyers, Sutter, Alexandrescu, Langr, Feathers, Stroustrup, Lakos etc) that I have read page to page. However, I am certain that any sufficient C++ developer can embarrass me by showing me a corner of this language I have never experienced before. It just never stops. The things I have to keep in mind while coding a solution for the actual problem at hand can be astounding.

But then, I really like coding in it as there are these rare cases when I’m coming up with an elegant and straight to the point solution. I think I have some kind of Stockholm love-hate relationship with this tool of choice.

For my consulting projects, I've found that Halide[1] is a worthy game changer when it comes to performance consultations, due to their architectural decision of separating between code and their scheduling (or algorithms and execution).

Whereas previously I had to run careful benchmarks and profiling for a given target hardware, I can play with different scheduling approaches or even run their DL based autoscheduler to get me quickly in to the 90th percentile of where I want to be.

[1]: https://halide-lang.org/

Given that any stock is a function over time as well, there should theoretically exist a neural net that can approximate the stock price for the future? This reasoning is obviously wrong, what is my exact error of thought though?

Thanks for pointing this out as I share the same opinion regarding Lex. For me personally it‘s that his behavior during his podcasts doesn’t match up to the intellectual shallowness of his questions and thinkings which drives me a bit crazy, e.g. a deep concerned look, a long pause and then.. an obvious statement or something along this line

The most recent computerphile YT video [1] is talking about the inner workings of git (Inside the hidden git folder) which I found quite interesting. Anybody reading this that came across some previous article about how git works and couldn‘t be bothered (just like me) may find this interesting.

[1] https://youtu.be/bSA91XTzeuA

In my experience (and coming just out of a meeting alike) these types of respectful and forward-moving meetings are typically in a case where each attendant has roughly the same level expertise in a given domain and knows the basics of scientific principles. Hence, everybody in the meeting brings in his or her unique view of the topic at hand and knows intrinsically when it makes sense to contribute something to the discussion. Usually things get out of hands, if somebody is talking just for the noise or, and this is worse, a clearly bad idea wins the discussion because politics or the messenger has shouted the loudest.

Which stands for What The Flux, obviously ;-)

I interpret OP‘s comment rather as an intersection, not a union of the targeted dev group. Your last sentence however sounds passive aggressive to me, which I rather don’t want to read here on HN

I'm a freelancing software consultant from Germany that gets increasingly spammed from UK recruiters and always wondered what the case is here. Your linked article pretty much nails it though. That being said things are only slightly different here in Germany, albeit not too much.

I just finished watching a really nice talk _An Evening with Leonhard Euler_ [1] that discussed a small fraction of his work and the massive amount of papers he produced (hundreds of which were only published after his death)

[1] https://www.youtube.com/watch?v=h-DV26x6n_Q

Pretty much standard procedure nowadays. The search term for this is TAVI (Transcatether Aortic Valve Implantation)

Unfortunately, these calculators usually only do work for US citizen. I‘m from Europe (or Germany rather) where there are a lot of different factors needed to take into account in order to get a realistic number (legal pension fund etc.)

I think this approach is very similar to how Android is handling the different apps where each gets installed into its own dedicated path directory. (I may be wrong though, cant remember since the last time I‘ve looked into the AOSP)

I‘d argue that one should not compare editors to IDEs as they are not comparable. I was using VIM professionally (i.e. at work) for many years until CLion showed up. Sure enough I could get around in VIM using many LLVM tools such as clang-rename, clang-format, clang-analyzer etc. but an IDE is doing much more (of rather is capable of) than editing text efficiently.

I appreciate that the author was looking to solve this problem using a _classical_ CV approach just like in the good ol‘ days as opposed to just train another ANN that predicts the time for a sufficiently large training set.

As for the detection of the hands itself: I think I‘d try to look for them in fourier space to get a more robust result (to address noisy dials like in the last examples).

For our german audience here at HN, there's also a (german) version called Bastard Assistant from Hell (BAfH) [1] which I can highly recommend if you liked the original stories as well

[1] https://de.wikipedia.org/wiki/Bastard_Assistant_from_Hell

I think we should rather talk about the (history) of working the typical 8 hours a day, which doesn't make much sense for software people if you ask me. IIRC the concept of working 8 hours is more than 100 years old and was considered an optimal value to minimize the number of work accidents and burnouts (for factory workers) and allow for three shifts per day. Hence, 8 hours was (is?) considered to give optimal efficiency for any worker.

For me on the other hand, I cannot do any deep work for more than 3-4 hours during a normal day. However, to comply to the historic 8 hours work day, the rest of the day gets filled with __other__ stuff, which may or may not is reasonable.

As others have mentioned already, I think it totally depends on company size, culture and people if you are able to gaze through a day by doing only a few hours at any given day. This completely coincides with my experience as well.

I never understood the argument of _helping fellow developers out_ by setting up their development environment or _lowering the entrance bar_ as everything got so complicated really.

For one, I personally cannot trust the technical competence of a fellow developer if he/she cannot handle their setup him/herself. We're talking installing tools by clicking around, aren't we? The same argument holds true for a fellow plumber that has never worked with this pipe system in particular.

Second, there's much to discover by installing and setting up everything by oneself. It can give insights on how things are connected to each other tool wise which is the first step of getting familiar with a new environment in the first place anyways.

Computing in higher dimensions is nice, although pretty difficult to implement efficiently. Hence, Quaternions are mostly used nowadays, I think.

Great. I'm using grep.app[1] usually as for me the GitHub search is mostly useless. Your mileage may vary though. That being said there are many other great search interfaces that I am using often when I'm trying to find solutions to common problems or specific design patterns. Chromium search[2] comes to mind, Mozilla's Firefox[3], Android[4] or of course Google[5]

[1] https://grep.app/

[2] https://cs.chromium.org/

[3] https://dxr.mozilla.org/mozilla-central/source/

[4] https://cs.android.com/

[5] https://cs.opensource.google/

I clearly remember my heureka moment when I discovered back in university that I don't have to actually learn and remember all that stuff that was taught but to recognize patterns and tricks that will reduce the problem domain down to a few things from which everything else can be deduced. After that most of the lectures boiled down to: ok, what is important to learn and remember here :-)

Firefox has been using these hacks described in the article for quite some time now for its build command script mach[1]

[1] https://searchfox.org/mozilla-central/source/mach

Pretty neat, although its support for Windows hosts seems to rely on Powershell (or dispatches completely to anything other than Python. Not sure about that)

Unfortunately, the one in Wiesbaden, Germany closed soon after it opened due to low interest.

Pretty much in computer vision / image processing related companies and software products. The performance related advantage on Intel x86 architectures in particular is not to be neglected.

I am not doing _that_ type of number crunching in my daily work, so the following check (in Python) has probably lots of potential for improvement:

    def is_prime(n):
        return not True in [n%x == 0 for x in range(2, n/2)]

Obligatory reference to the mother of all demos [1] by Douglas Engelbart

[1] https://www.youtube.com/watch?v=yJDv-zdhzMY&ab_channel=Marce...

Every time this term comes up here, I have to think this is about Halide [1].

[1] https://halide-lang.org/

This breaks pretty easy unfortunately by simply drawing in reverse (e.g. draw circle counter-clockwise instead of clockwise etc.)