14
BooFar
6y

Sitting at traffic lights on my way home from work thinking about the programming behind how often the windscreen wipers are triggered, how to store the values of each wiper setting in a meaningful data type, and how to handle the event of changing wiper settings eg. to ensure the wipers aren't triggered immediately when increasing the frequency.

Wish my mind could rest when I'm outwith work but I experience this sort of thing worse after drinking alcohol. Must have a problem.

Comments
  • 3
    Everything is a coding challenge and that's why programming is so cool.

    As for wipers not being triggered when increasing the frequency, I prefer that it *does* trigger them. If I'm wanting to increase the speed it probably means the rain is coming down harder all of a sudden and I can't see. Wouldn't want to wait a whole cycle like that.
  • 1
    I kind of do it now and then as well and it's not a bad thing. By being analytical when it comes to even the minor things, you can derive those solutions and utilise them for other factors in your work or even life.
  • 2
    Everything is or can be represented as a data structure or an algorithm. Everything.
  • 0
    @Ancalagon I like to think that its just chained-macros
  • 0
    But is the data used to trigger the wipers processed and stored in compliance with GDPR directives?
Add Comment