FlyingAvatar

You can keep using the hardware, but you will be blacklisted from their online services.

Really wish they would allow creating limited scope API keys though. You can only limit keys by domain, not by action or record which would be ideal.

Think the the unread count for GMail or the new message notification badge for Slack. It's worked this way in Firefox and Chrome for almost 2 decades. We're past the "you're doing it wrong" timeframe, in my opinion.

The one thing that keeps me from using Safari is web apps can't update their tab's favicon. That means if you load a site that uses the favicon for notifications you either (a) login when you have a notification and it will now forever seem like you have a notification or (b) login when you don't have a notification and it will forever seem like you don't have any notifications.

Yes, you can clear a cache for a one time update, but that is hardly helpful.

A friend and I built our first "game" in Turbo Basic. It was fairly capable and being able to make an EXE out of a basic program felt like magic when GW-Basic and QBasic were the only other basic's we were had ever used on a PC. Several years later VB for DOS was also pretty impressive with a text-mode form designer.

Operation Overkill

Burning capacitor electrolyte

From watching his videos, he's an Apple guy for his personal devices, though his server infrastructure (and also the bulk of the devices he reviews and experiments with ) are Linux machines.

They are low earth orbit satellites. Generally, the lower the orbit, the faster they decay. You could also argue that this is a benefit in that they gain updated technology with each replacement.

1. I would login to my favorites daily. I ran my own BBS (using the Renegade BBS software) as a teenager, so would monitor that as well. I think I landed on QModem after using Telix.

2. I knew friends who used them but we had the RIBBS list (Rhode Island BBS List). What was amusing at the time (90s) is that despite Rhode Island being the smallest state, there were still "local long distance" calls that cost money to make, so you had to be aware of what numbers you were able to call for free.

3. "Boards" were the terms we used, the term "server" was not in use that I know of for BBS host machines (despite them being essentially servers). There were definitely more popular ones, but also ones that served specific niches (photography, gaming, role playing). One of the more popular ones in RI got shutdown for hosting pirated games. The pirate stuff was never visible to my account, though they did advertise having GB of files available. This amount of data was huge compared to the 120MB hard drive I had at the time.

4. The vibe was variable based on the BBS. My impression was that the early internet had a better vibe than BBSes, because they were relatively small and regional you mostly got the discussion that was happening in your own locale. National BBSes were certainly a thing as well as services like GEnie and CompuServe, but those weren't something I frequented.

5. Honestly, I didn't see a lot of programming discussion. I am sure it was there, but I wasn't seeking it out. From a technical standpoint, a lot of it was talking about the new hardware of the day and also discussing BBS operation and configuration.

I am a former Directory of Technology for small/medium business who has transitioned to freelance work three years ago.

Open to fractional CTO (particular interest in non-profits) roles, AI/LLM process integration and web/mobile app development projects.

  Location: Rhode Island, USA or REMOTE
  Remote: Yes
  Willing to Relocate: Mostly no, but possible for the right opportunity
  Technologies: Vue/Vite/Pinia, HTML/CSS/JS, Python, AWS (S3/Lambda/CloudFront/Dynamo/RDS)
                OpenAI/Anthropic APIs, Security/PCI audits and compliance 
  Resume: https://www.linkedin.com/in/andrewjbent/
  Email: gmail - andrew.bent

Disclaimer: I'm not the OP, and there are certainly places where using recursive type definitions is justified.

My interpretation of OP's point is that excessive complexity can be a "code smell" on its own. You want to use the solution to match the complexity of the job and both the team that is building it and the one that is likely to maintain it.

As amused as I am by the idea of a dev team being debased by the inelegance of basic bitch programming, the daily reality of the majority of software development in industry is "basic bitch" teams working on "basic bitch" problems. I would argue this is a significant reason why software development roles are so much at risk of being replaced by AI.

To me, it's similar to the choice one has as they improve their vocabulary. Knowing and using more esoteric words might allow adding nuance to ideas, but it also risks excluding others from understanding them or more wastefully can be used as intelligence signalling more than useful communication.

tldr: Complexity is important when it's required, but possibly detrimental when it's not.

I don't really buy the comparison. If you're really unlucky, you can get cancer from a "safe dose" of radiation.

Low exposures of both things are statistically less likely to hurt you than large doses. We pick a line to call "safe", but completely safety in either case is not guaranteed.