magic_lobster_party

deleted by creator

It’s confirmed real by other (less serious) news sources.

It was a few years ago, but I still panic when I hear the incoming call sound. One of the worst sounds ever made.

Now it was a few years ago I used it regularly last time, but moving to Slack was a huge relief.

One thing I remember with teams is that sending files was always a hassle. Sometimes files didn’t arrive. Files couldn’t have the same name as other previously sent files (because everything was in a onedrive folder).

Slack has much better search. It felt like I could finally find the messages I wanted to find. With teams it was a gamble.

And then there’s much better bot integration. At my work we have multiple bots that send messages when there’s e.g. production errors. We can then start thread discussions directly on that posts about the error, or link it to other channels to escalate the issue. And with a working search engine we can easily find the conversation again as a reference.

It got many small things that just adds value.

Oh so it’s finally useful again? I don’t know how many times I’ve installed the thing only to realize I don’t want to set up an account.

There are rumors which suggests HL3 is currently in development, so we’ll might see soon.

Math skills can occasionally be useful, but I don’t see it as a dealbreaker.

The good thing about being good with math is that it usually means you’re a good problem solver, and problem solving is an important skill for programming. But the reverse isn’t necessarily true. You can be good at problem solving but still be bad at math.

I would say if you’re struggling with the programming courses, then maybe look somewhere else. Otherwise, go ahead.

Python is truly a mess when Docker is considered a solution.

Nothing comes close to Perl’s abuse of global variables. Oh you called this function? Take a guess which global variables it will use.

Do you know why?

The type is dynamic. It can be whatever you wish.

From the original document:

Software manufacturers should build products in a manner that systematically prevents the introduction of memory safety vulnerabilities, such as by using a memory safe language or hardware capabilities that prevent memory safety vulnerabilities. Additionally, software manufacturers should publish a memory safety roadmap by January 1, 2026.

My interpretation is that smart pointers are allowed, as long it’s systematically enforced. Switching to a memory safe language is just one example.

Apparently it’s super successful. Has made $3 billion within a year.

TAOCP is a misleading title. It shouldn’t be computer programming. It should be computer science.

For most people, programming is the engineering discipline. I think that’s a very different art form. Software engineers are rarely dealing with the type of problems TAOCP is concerned about.

Squadron “Feature Complete” 42

I’m mostly working in Java now. I’m proficient to the degree that I can solve most things without looking for reference online. I think that matters most to me.

OO languages typically use garbage collector. The main purpose of the borrow checker is to resolve the ambiguity of who is responsible for deallocating the data.

In GC languages, there’s usually no such ambiguity. The GC takes care of it.

Sounds like you’re thinking more about the builder pattern.

Mainstream statically-typed OOP allows straightforward backwards compatible evolution of types, while keeping them easy to compose. I consider this to be one of the killer features of mainstream statically-typed OOP, and I believe it is an essential feature for programming with many people, over long periods of time.

I 100% agree with this. The strength of OOP comes with maintaining large programs over a long time. Usually with ever changing requirements.

This is something that’s difficult to demonstrate with small toy examples, which gives OOP languages an unfair disadvantage. Yeah, it might be slower. Yeah, there might be more boilerplate to write. But how does the alternative solutions compare with regards to maintainability?

The main problem with OOP is that maintainability doesn’t necessarily come naturally. It requires lots of experience and discipline to get it right. It’s easy to paint yourself in the corner if you don’t know what you’re doing.

Even when computers did improve and became able to handle Vista people weren’t willing to change their minds about it. Windows 7 had a 1GB memory requirement. Why didn’t more people use Vista right before the Windows 7 launch?