magic_lobster_party

  • 0 Posts
  • 43 Comments
Joined 3 months ago
cake
Cake day: August 15th, 2024

help-circle





  • 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.







  • 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.






  • 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.