In my last job they required us to turn on a task timer for every little thing. Remembering to do that, and to turn it off, was a royal pain. First I had to look up which task it is, start the timer, stop the timer, find the next task and repeat, then flip back to the first task. Lots of open browser tabs within tab groups to keep track of it all. And if I came up short or went over on budget, there was a “conversation” with management to account for discrepancies. Then I had to go by memory and try to reconstruct the “missing time” accurately enough to be convincing.

Now that I’m freelancing, I try to keep up the habit because it does have merit for tracking estimates and actuals, but now it’s just me to answer to for discrepancies and I can fudge the numbers as I see fit. The time records did, however, save my bacon in a recent dispute.

Grrrr

I love JS, but I hate browsers.

Universal ES5 way to initialize a date from a input value in "dd.mm.YYYY" format:

var split = input.value.split('.');
var from = {};
from.day = parseInt(split[0]);
from.month = parseInt(split[1])-1;
from.year = parseInt(split[2]);

var myDate = new Date(from.year, from.month, from.day);
// if a timestamp format is needed:
var myDateTimestamp = +new Date(from.year, from.month, from.day);

No, I won't use moment.js or other bloat-braries just for fucking dates.

ChatGPT is so much better than Google:
instead of wasting my time by linking to unhelpful / outdated / unrelated StackOverflow resources, it tells me to do the work by myself right away:

> To ensure consistent pseudo-element width across different browsers, including Safari, you can follow these steps: [...]
> (some basic HTML/CSS 101 seemingly quoted from a 2015 textbook)
>
> It's important to note that browser behavior might vary due to different rendering engines or versions. While following best practices helps achieve consistent results, you might still encounter small discrepancies. Cross-browser testing is always recommended to ensure your design looks consistent across different browsers, including Safari.
>
> For any specific issues you encounter in Safari, consider checking for known bugs or quirks that might affect pseudo-elements and their sizing. Online resources, developer forums, and documentation can provide valuable insights into Safari-specific behavior and workarounds.