• 2 Posts
  • 44 Comments
Joined 1 year ago
cake
Cake day: July 3rd, 2023

help-circle



  • I was thinking (from reading the headline) that if one specific component fails 15 times during boot or so, it will just automatically get disabled by the system, so that you don’t run into an unavoidable boot loop.

    But this makes sense as well, if they did write “up to” in the article (as others have stated). Even though I find the confidence weird. Imagine you have some weird dial-up or satellite internet solution for your system, which just needs time to connect, and then maybe also just provide a few bytes/kilobytes per second. This must be rare, but I’m 100% confident that there exists a system like this :D

    Edit: okay, I should read first. The 15 times thing is said for azure machines.







  • Well, if it gets the job done. I’d only argue about maintainability there maybe, as other devs get involved.

    In my final apprenticeship work, I also only used vanilla php and argued that it would take too much time in this project to evaluate and learn a framework and that I know the vanilla way pretty good, so it’s valid this way around.









  • Last year I had a module for ai stuff. We did things in Python and I am quite into doing things as coding standards say. My mate didn’t really care so much and just went for his style of doing things, also not really worrying about descriptive names etc.

    Well, let’s say, we weren’t having a good time.

    I also realized that I was probably too harsh and tried to go a bit more easy on it later, but many things just felt wrong.