SoyViking [he/him]

  • 1 Post
  • 13 Comments
Joined 4 years ago
cake
Cake day: November 4th, 2020



  • I get your point about how individualised development is part of the problem. I just want to point out how these rituals to divine the future of a project can become absolutely cursed when done as a team effort. Sitting by yourself and pondering how long it will take to make the computer go beep is a miserable experience, having to discuss the minutiae of how long something will take because management got the idea that this will make the estimates “more accurate” is many times worse.



  • I worked on such a project in my old job. The application was the core product of their business and it was a sprawling mess that had evolved from constantly adding layers to a small proof of concept application.

    There was never time for anything other than adding new features. You never got to fixing the architectural flaws or streamlining things. We couldn’t even fix the ugly and confusing UI that every customer was complaining about.


  • There’s an old saying that a pig doesn’t get any fatter by being weighed and there’s a lot of pig-weighing going in the software industry.

    To me personally scrum rituals like daily standups are a minor nuisance. They are unproductive and often boring but most of the time you can get them over with relatively quickly.

    What I really, really, really hate is the time registration tyranny where you have to do estimates, have meetings about estimates, remember to turn on and off timers, fiddle with timesheets when you forget about the timers, answer questions like “how will this change that everyone agrees needs to be done affect the estimates?” and defend why a task that was estimated to six hours took eight to complete.

    I have ADHD, I have trouble making a realistic estimate on how long it takes to cook pasta and you expect me to be able to accurately predict how long it takes to compete a 3000+ hour project with a ton of external dependencies, arcane legacy code and agile constantly evolving requirements?

    I understand that you need something to put on a bill that the customer will pay without complaining but come on, how can this be effective? Sometimes I feel I spend more time wrangling timesheets than actually coding.





  • The closest I can come is blackletter or fraktur scripts that were once used for generic languages. As far as letters go they are silly and overcomplicated, with Latin scripts being far easier to read and more adaptable to different visual styles.

    With that being said, they do have their own old-timey charm and there is something satisfying in being able to pick up a old book in blackletter and read it when you know that most people can not.

    Fun fact: Blackletter was only used for Germanic languages. If a text contained non-Germanic passages it was normal to set those in Latin letters while the rest was set in blackletter.




  • Someone I knew was living in an old building with old-timey fuse boxes placed outside the apartments. When she got tired of her idiot neighbours partying on a weekday night for the millionth time despite being asked to dial it down she finally had enough and went to the fuse box and took away all the fuses to the neighbour’s apartment.

    She never had trouble with noise again.