In the morning you copy your calendar by hand to the pocket mod? What about dynamic event changes (e.g. additions, subtractions and reschedules)?
There’s something more optimal than my current attempt at strategic daily itineraries (which is quite poor) - a tug between the mechanical and the breathing, flexible and organic.
A Pocket Mod is an 8 page book. I use two pages in Calendar format for big events, ie Birthdays, dinners, doctors, etc.
My calendar is pretty much set for the week. There are 4 pages that cover the weekly schedule, 2 days per page. There is blank space on the bottom half of the last page to put reminders for the next week.
This leaves me 2 pages for todo-lists.
You can make the 8 pages anyway you want, print them as a 8 page PDF document. The Pocket Mod program then rearrange the pages into the right format for folding.
If I need to create a new one it's under a minute to run the process, fold and cut the book.
I’ve been checking every couple weeks for a status update on Fresh for the last six months (others have been checking longer, it’s a vocal set of early adopters on GH and discord!).
I’m not even sure I’d have confidence in adopting Fresh, but I definitely was using it as a canary for the Deno org’s health. If they can’t maintain their flagship front end framework, after all, they must be circling the drain?
If that’s not the situation, I’m bewildered by their approach to communication.
Anyway, I’m still left wondering if Deno will be around in 18mo. It’s generally a nice DX, but so risky to bet on. I want them to succeed, but fear they won’t.
On mocking your database transaction: I was there, and on behalf of an LLM I reasoned with, I refactored that bit out to be an actor that carries the transaction, and passing messages (alongside a oneshot channel for return value). The benefit isn’t just that you’re not managing a transaction, but also that you don’t need to coordinate the transaction between multiple async paths where lifetimes and ownership really blow up!
I didn’t use an actor framework, for better or worse, but rolled my own.
Because of the cost. Performance (if you optimizer is any good) will be at most a few thousand CPU cycles and so only rarely worth worrying about, though even this can add up if everything is an interface.
The larger cost is maintenance. Every time you want to change/add/remove something you now need to touch not only every place that uses the thing in question, but also all the tests. That is by mocking your are tightly coupling your tests to how your code is implemented instead of the code should do. If there is more than one implementation this is okay as the code can do different things in different situations anyway, but if there is only one then you are adding coupling that isn't useful.
If you have never worked with non-trivial code that is more than 10 years old the above won't make sense. However as code ages you will discover that the original beautiful architecture ideas where always wrong for some need that happened since and so you have had to change things. Mocks make all those changes much harder.
You apparently have never been in the situation of making a trivial change to production code and then have thousands of tests fail because of overuse of mocks.
> For those looking to transition into leadership,
My biggest pet peeve in this industry is the self anointing of the “leadership” attribute.
Its management. Just management. Some managers may be leaders, but most aren’t. Some ICs may be leaders. Most aren’t. Some politicians may be leaders, but most aren’t.
Or maybe I just never grasped what leadership means. Either in the context of the world or our industry.
Go Irish.
reply