• 0 Posts
  • 94 Comments
Joined 1 year ago
cake
Cake day: June 18th, 2023

help-circle


  • There are two common types of laser printers. Those that have special paper that react to heat, such as receipt printers, would fit the description.

    The other laser printers… Hm, I don’t think your description is accurate either. It’s more that the laser electrically charges ink particles so that they jump on to a separate roller that gets rolled on to the paper.

    I’m no expert though.




  • Absolutely. Those you suggest there are good examples.

    Good enough that, instead of “is/isn’t” programming language, it would be more a “ah, so, how do you define that then?”. Now that I’ve had some sleep, one could argue that I could have been nicer and suggested that approach for HTML as well. After all, it’s just words that mean stuff, and transfer a concept between people, that translate to the same (ish) idea. The moment the latter isn’t the case, it’s no longer very useful for the former.

    Most disagreements, I find, are just cases of different understandings. Discussions worth having is when both are correct but different, and both want to figure out why they differ. So, on second thought, I think I was appropriately rude _

    Both LaTeX and roff are Turing complete, but they are also DSLs with a somewhat narrow “domain”. Sounds exactly right that these blur the lines between what is/isn’t. You could even argue that claiming one or the other is just one way to express how you understand that difference.


  • That’s such a weird point to make. Is it because to you, it seems like the line drawn is arbitrary? I cannot imagine any other reason. Certain words just mean certain things.

    Markup languages are exactly as much “programming” as you marking a word and hitting “bold”. Which is to say, nothing at all. People are wrong all the time, and I have a very limited amount of fucks to give when it happens.

    As for Scratch, it is a programming language. So, why would you think it’s a logical next step for me to say otherwise? Next, you’ll say something remarkably dumb in response. Resist the temptation, and do something more productive.





  • Only losing a week on a major change is a good sign. I wish the people who started the project had that same attitude with regards to clarifying requirements. They also did the opposite of designing a flexible solution. No thought to the actual problem, picking a contrived problem to “tackle”. Full on blinders on event driven architecture, split a simple thing into multiple nano-services, yet tightly coupled by sharing the same model which is de/serialized at every step, and then throw in application level filtering on the events… no schemas, no semantic versioning.


  • waiting for solid requirements

    This is exactly the situation. Except that my team consisting of consultants just “started”, instead of trying to scope out the constraints and larger picture. I joined a month or so after.

    Six months, and the result so far of their exploration is a fairly uninteresting happy-path use of some technologies, barely related to the task that had unclear requirements. Turns out the work done is unsuited for it. Boggles the mind how much resources are wasted on such things.

    Feels extremely unrewarding to have worked, relatively hard, for half a year, and the fruits of my labour is… getting to the point where the actual problems are solved. Which one could have done from day one, if one had started in a team without wrong preconceptions, or, no team, for that matter.






  • It’s fascinating how some SPAs come about. Often consultancies who win some bid to implement X features. Since “good user experience” is hard to quantify/specify, it ends up being a horrible end result.

    Zalaris is one such that I’m in complete awe of. Set up user flows that are expected to take 30 minutes to complete. Yet, don’t keep track of that state/progress withing your own SPA. Click the wrong tab within that SPA, and state is reset.

    It’s, just fascinating.



  • Here is a list of some practical uses so far:

    • Get a notification on the phone when the washer is done.
    • Charge the car when electricity is cheap
    • Turn on humidifier if sufficiently humid and no motion near it for a while
    • Automatically lock the front door at night
    • Toggle lights with a shortcut key on the keyboard
    • Change target thermostats for different rooms and different time of day.

    Also nice to learn about the house:

    • Breakdown of electricity usage. (How much actually goes to heating, car, etc)
    • Answer questions like “When did I really go to bed last night?”. Etc