I once collaborated with an exceptionally talented programmer who seemed so engrossed in his addiction that he would invent challenges where there were none, presumably to make his work more engaging and bearable. However, this often led to incomplete projects because once the stimulating aspects were finished, he struggled to find the motivation to continue. Clearly, this behavior was extreme and detrimental.

I think a lot of devs can relate to that

Who cares if the program has done its job anyway

This works a lot of the time with the people that don’t really care about the review. With those that do it won’t

Focusing beyond the code - as a developer you will code 20% of your time.

Doesn’t sound like a great software engineer to me

In my company everyone is called Software Development Engineer 🤷‍♂️

If you can do it in 2-3 months it’s worth it, else you’re probably not getting paid enough

Basically, they won’t bother sueing you unless you end up making millions off it

But at that point the program will likely not even be reminiscent of its original form

started up notepad, which was the only application it was capable of running

Coding a linked list in C in Notepad and only one syntax error? This guy’s worth the money!

Even less so now that docstrings can be mostly written by AI

whoosh

Sounds like a great DRY culture to me

Industrial workers in the 20th century probably never imagined being replaced by robots, but it’s happened on a large scale.

There’s still plenty of industrial workers. The same will be true for programmers as AI proliferates.

These jobs don’t go away, they just become more specialized

But I will agree with the general notion that we as programmers are incredible fortunate to be able to work from anywhere, creatively, without physical labor

It does. OSS needs visibility, it needs contributions

GitHub’s community and discoverability features really help with that, as much as it sucks that they got acquired by Microsoft

Let’s be honest here, at least like 98% of the popular OSS is on GitHub at this point. You don’t have to like it, but it’s how things are

Wow that actually sounds really helpful. Didn’t know you could do that. As always, best content in the comments

Can you not add an ingest throttle / queue before the writes hit the DB? But sounds like a management problem to me honestly

I don’t want to know how many rushed games so stuff like this

Very high effort reddit screenshot repost

I mean nice, but anyone with half a brain will take a look at the code and decide for their own if they’re a decent coder

Also there’s star graphs over time that show the growth of a project

Yeah, this one really had me scratching my head:

✓Note: there are lots of ways we could make the Python code faster, but the point of this post isn’t to compare highly-optimized Python to highly-optimized Rust. The point is to compare “standard-Jupyter-notebook” Python to highly-optimized Rust.