magic_lobster_party

  • 0 Posts
  • 77 Comments
Joined 1 month ago
cake
Cake day: 15 August 2024

help-circle
  • What’s happening is that support from VC money is drying up. Tech companies have for a long time survived on the promise that they will eventually be much more profitable in the future. It doesn’t matter if it’s not profitable today. They will be in the future.

    Now we’re in a period where there’s more pressure on tech companies to be profitable today. That’s why they’re going for such anti consumer behaviors. They want to make more with less.

    I’m not sure if there’s a bubble bursting. It could just be a plateau.





  • I didn’t read everything, but I mostly agree with the author, especially on this point:

    While you can definitely abuse exceptions, functional-style error values are not a one-size-fits-all solution.

    There are time and place for both. I think exceptions are good for bigger errors. Like database connection errors. Things that shouldn’t happen without any easy backup plan. Those errors might need to be escalated as high as possible where proper action can be made (like resetting the database connection and everything relying on it).

    Functional style is great for smaller stuff. Like key not found in hash maps. In many cases there might be good defaults that can be used instead.



  • Haven’t read through this, but this sounds like what C++ is to C. I’m not sure adding more complexity and features to an already complex language is the right way forward. What is needed is a language that cuts down all the burden that has accumulated in C++ over 3 decades.

    Something like Zig sounds like the better path forward to me. A completely new language from scratch with cross interoperability to C++. I’m surprised it’s not mentioned even once in the page.








  • I agree, and I count that as “key information that’s difficult to understand from the code”.

    IMO, comments should be used to provide value to the code. If they’re used too much, then readers of the code will more likely stop reading them altogether. They already got what they need from the code itself and the comments usually don’t add much value.

    If they’re sparse, then that’s a good indication they’re important and shouldn’t be missed.




  • I think comments are good as a last resort when it’s difficult to communicate the intention of the code with other means.

    If I find code that’s hard to understand, I’ll first try to find better variable or function names. Often this is enough.

    If it’s still too difficult to understand, I try to restructure the code to better communicate the flow of the code.

    If that doesn’t help (or is too difficult), then I might add a comment explaining key information that’s difficult to understand from the code.