If you want to remember dates, how about a calendar printed on paper? A filofax?
Generally these days, the best solution is one that doesn't involve computers and big tech.
2,798 karma · joined November 22, 2014
Generally these days, the best solution is one that doesn't involve computers and big tech.
Idle time can still be incorporated, it just has to be _in_ the tickets, not between the tickets, then everyone is happy.
A ticket for one day to add a new button, then an idle day is bad. A ticket for two days to add a new button keeps everyone happy.
The right-to-left scripts/languages are relatively esoteric, and their market share probably rounds down to 0 for Google.
It's almost as if... there is some other rationale at play for sending ICE there?
At MegaCorp, there is a never ending arms race between security/compliance teams locking things down, adding approval and surveillance checks, and everyone else just trying to do their job.
Usually there are workarounds and backdoors available to people in the know. If you kick up a fuss, you'll be seen as "difficult". A key part of the job is finding tricks to get things done _despite_ all of the rules / checks in place trying to protect you from yourself.
It feels like programming then got a lot harder with internet stuff that brought client-server challenges, web frontends, cross platform UI and build challenges, mobile apps, tablets, etc... all bringing in elaborate frameworks and build systems and dependency hell to manage and move complexity around.
With that context, it seems like the AI experience / productivity boost people are having is almost like a regression back to the mean and just cutting through some of the layers of complexity that had built up over the years.
Files are pretty handy. It's a bit surprising how many people seem to have forgotten they are a thing... but not that surprising, given how hard big tech have tried to uninvent them.
I've tried to go back to that a few times, but it's actually pretty hard to do these days. After a few decades of trillions of dollars of investment, pretty much every tiny niche has become a company / app with dozens of developers, or available as an online customizable SaaS, or something that can be vibe coded.
There is really no point in worrying about personal independence for smart phones, github hosting and operating systems if the state itself is not independent and self-sufficient.
I wonder if all this shoving of AI down peoples throats could trigger a bit of a backlash around vendor software updates / proprietary software in general. There's this huge infrastructure of Windows Update, chrome auto-updates, app stores and SaaS that predated and enabled all this... and people accepted it when they were getting bugfixes and security updates out of it, but now it's getting used to take away the features they wanted and replace them with worse and worse versions of crapware.
All of a sudden... the free software world of updating when _you_ want the new version, and being able to fork the old version if you want, starts to look pretty great.
Maybe think about whether what you propose could exist as a compiler warning, or static analysis tool. Or, if you want to create your own language, go for it, that's cool too.
For my purposes... the choice of paradigms, compilers, platforms with C++ and ability to handle and work on decades of existing code outweighs the benefits of "improved" languages, but that's just me.
In C/C++, this can be done by just not using malloc() or new.
You can get an awfully long way in C with only stack variables (or even no variables, functional style). You can get a little bit further with variable length arrays, and alloca() added to the mix.
With C++, you have the choice of stack, or raw new/delete, or unique_ptr, or shared_ptr / reference counting. I think this "multi-paradigm" approach works pretty well, but of course its complicated, and lots of people mess it up.
I think, with well-designed C/C++, 90+% of things can be on the stack, and dynamic allocation can be very much the exception.
I've been switching back and forth across C/C++/Java for the past few months. The more I think about it, the more ridiculous/pathological the Java approach of every object dynamically allocated, impossible to create an object not on the heap seems.
I think the main problem is kind of a human one, that people see/learn about dynamic allocation/shared_ptr etc. and it becomes a hammer and everything looks like a nail, and they forget the prospect of just using stack variables, or more generally doing the simplest thing that will work.
Maybe some kind of language where doing dumb things is an error would be good. e.g., in C++ if you do new and delete in the same scope, it's an error because it could have been a stack variable, just like unreachable code is an error on Java.
I don't really think "typo" is a useful word in this context. It's a sequence of characters that... _does not work_ and _was not tested_. The fact that it is close to a different sequence of characters that would work, or that a human could recognize it for that other sequence, isn't really relevant.
Some of the engineering approaches you mention can help, but at the end of the day he has to be responsible for verifying that things work. Tests, schemas, etc. can help, but you don't want to get into a game of "the test/linter/AI didn't catch this for me, therefore it is broken".
I've worked with plenty of people over the years with linguistic quirks, like spelling insisting on spelling "deliminator", or "pluggin", or whatever, but if the code works, it works.
The narrative is that human labor is expensive super expensive, there are "skills shortages", etc etc... but in actuality, hiring a few people rounds down to 0 in the context of an airliner or an office building in Manhattan, and you get a lot of political sway for employing folks and paying payroll taxes, and the "doorman fallacy" is very real. The "robots taking our jobs" narrative seems hugely exaggerated to me.
I use https://en.wikipedia.org/wiki/KeePass
You can store the other details in the notes - e.g. which card / account is used for payments, what are the password reset questions & answers, which address is set for delivery.
Then, when you change credit cards / addresses / emails, etc., it's easy enough to find all the accounts you used the old one for and need to update.
Every product with users is now a merely channel for shoving the vendor's AI down the user's throats.
After that, "security" starts to mean "ticking all the boxes to keep the scan happy and stay off the report" (even if the scans are wrong, out of date, littered with false positives, and lacking the ability to find basic problems) and stops having anything to do with actually being secure.
I was reminiscing about how much dual monitors used to be a pretty standard thing, and definitely pretty helpful when economical monitors maxed out at 1920x1080, but seems much less prevalent these days. Not too surprising I guess considering the costs, space consumption, hardware, cables, etc etc.
The reality though is that for most businesses, the hard part is customer acquisition, marketing, logistics - for a restaurant, site selection, decor, etc... if you get that right, you can probably solve your staffing problems pretty easily by just being 50% overstaffed, and using a whiteboard and post-it notes. If you _don't_ get that right, then no amount of efficient shift scheduling can save you.
Just a thought.
You don't own the page. Facebook owns it. You _authored_ the page, and _gave_ it to Facebook, and now they can do anything they want with it.
Step 1: Ask for, and obtain your medical records from your providers.
Step 2: Once you have your medical records in your possession, keep them organized, and share them with whoever you want, whenever you want.
I just keep them like one directory per doctor/provider, and dated filenames like dr-foo/2023-02-24-chest-xray.pdf or whatever.
Patients have an absolute right to their medical records, test results, with very few exceptions. It is _not_ hard to get access, just ask, and if you have any trouble, talk to whoever hands out and takes away the medical licenses in that jurisdiction.
If you have all your records, its easy to switch providers whenever you want, get second opinions, and do your own research. It can be pretty interesting seeing the raw notes from doctors, getting the DICOM files for x-rays/ct/mri imaging too.
Just keep, and take responsibility for your own data, it is not realistic to expect providers, the government, or any business to do this for you.