• 0 Posts
  • 47 Comments
Joined 3 years ago
cake
Cake day: July 1st, 2023

help-circle
  • I have a more mixed approach.

    Decisions or attempts, i try to document them as comments on the ticket. It feels a bit like a conversation with my future self 😄

    Things that pop up in my head that I don’t want to forget, but don’t have time to write out, I put in a new tab on nodepad++

    Archi things go as markdown in de source code

    Investigations and reports in a wiki

    All these have all the pros of an engineering handbook out of the box (date, issuer, …)

    I only use paper for the stuff I don’t want a trail off and just want to throw away afterwards.



  • I think they especially make sense for records so you can easily create shallow modifyable value semantic types with little boilerplate code.

    I do hate that all these features are yet more keywords and weird syntax. It’s becoming C##.

    Like the records are just sytesized methods on classes or structs. We already have this in the language with source generation. If something there was missing to create records, it would IMO make more sense to improve the source generation so the community also has access to the ecmxtensions. And the record could be split up in it’s separate features (copy constructor, defaul ToString imp, equatable) so we could choose to use part of it.










  • If they need permission for third party cookies and those are now no longer possible, the popups can go already.

    And if a site doesn’t want to serve people that do not accept data hoarding, an account with terms and conditions is the only logical way to go.

    Belgium forced facebook to not track users without an account and they reacted by doing this exact thing (requiring an account to even read pages). It made it a lot easier for me to not having to deal with Facebook at all. If some store or organization only had the info on Facebook, I’ll just tell them I can’t access it 🤷‍♂️


  • Other package managers, like nuget, throw errors if all dependencies on a package cannot be met by a single version.

    This is probably the result of it copying all libraries in the same output directory and that .net cannot load 2 different versions of the same library so more an application restriction.

    The downside of this is that packages often can’t use newer features if they want to not block the users of that library and that utility libraries have to have his backwards compatibility so applications can use the latest version while dependent libraries target an older version. Often applications keep using older versions with known security issues.



  • This is unthinkable in the EU. If a company isn’t sure about the needed force, they need to hire temps.

    If you don’t have a technical or economical reason, you are not even allowed to lay off an employee.

    And you have to give notice for a period, which is proportional to the time you worked for the company, or you have to pay this fully as severance and this can be more than a year.

    Protected employees (voted as union representatives) are even harder to fire.

    This does come with the downside that some, almost not productive, colleagues never get fired. But I guess it beats the alternative of having almost no protection.