(Warning: This rant includes nonsense, nightposting, unstructured thoughts, a dissenting opinion, and a purposeless, stupid joke in the beginning. Reader discretion is advised.)

honestly the whole "ARM solves every x86 problem!" thing doesn't seem to work out in my head:

- Not all ARM chips are the same, nor are they perfectly compatible with each other. This could lead to issues for consumers, for developers or both. There are toolchains that work with almost all of them... though endianness is still an issue, and you KNOW there's not gonna be an enforced standard. (These toolchains also don't do the best job on optimization.)

- ARM has a lot of interesting features. Not a lot of them have been rigorously checked for security, as they aren't as common as x86 CPUs. That's a nightmare on its own.

- ARM or Thumb? I can already see some large company is going to INSIST AND ENFORCE everything used internally to 100% be a specific mode for some bullshit reason. That's already not fun on a higher level, i.e. what software can be used for dev work, etc.

- Backwards compatibility. Most companies either over-embrace change and nothing is guaranteed to work at any given time, or become so set in their ways they're still pulling Amigas and 386 machines out of their teeth to this day. The latter seems to be a larger portion of companies from what I see when people have issues working with said company, so x86 carryover is going to be required that is both relatively flawless AND fairly fast, which isn't really doable.

- The awkward adjustment period. Dear fuck, if you thought early UEFI and GPT implementations were rough, how do you think changing the hardware model will go? We don't even have a standard for the new model yet! What will we keep? What will we replace? What ARM version will we use? All the hardware we use is so dependent on knowing exactly what other hardware will do that changing out the processor has a high likelihood of not being enough.

I'm just waiting for another clusterfuck of multiple non-standard branching sets of PCs to happen over this. I know it has a decent chance of happening, we can't follow standards very well even now, and it's been 30+ years since they were widely accepted.

You know, I've really been thinking about renouncing my love for Microsoft's products. I got into the tech world through them, so their stuff was all I really knew. It's like a non-dev growing up using Mac and iPhone. You don't really know what other hardware and software can do (especially since Microsoft is now acting a LOT like Apple nowadays). Ever since they killed Windows Phone, I started seeing past the rose-colored glasses. They've annoyed me with one slip-up after the next. The only things that have kept me tied to them are my Windows Insider membership, and their developer platform. Now that I've seen things like Fuchsia and Linux, I realize that the way Microsoft is going about technology is painful to developers and consumers alike, and this is now beginning to hurt their bottom line. I'm sick of it.

The issue is that if I leave the Microsoft platform, I will have no time to waste. I spent the last 2 yeas cozying up to them, and now I will need to find other platforms, languages, and utilities to build a portfolio from. This also means that I will despise pretty much every major tech company for different reasons (Apple for locked-down hardware, Microsoft for locked-down software, Google for it's monopolistic actions and its unfair policies and terms, Amazon for its invasiveness, etc). If things get worse, I'll probably end up going to Linux and joining the open-source community. The only worry I have is what I'll do for a career. I'm almost halfway to getting an Associates in Computer Science, but where do I go from there? Can't make a living open-source (unless I get patrons, which is unlikely), will probably abandon my dream of joining Microsoft or Google, and I don't currently specialize in any particular area of development yet. I want to spend my life dealing with tech and software. But right now, I've got next to no plans. I've got a lot of thinking to do...

DataDevNerd (ofc down to hardware bits)
Briefly blending amoung holiday tech consumers at Micro Center waiting for key-holder assistance @SSDs.

Rando: "they finally have a sale on *X, rebranded, price++* for my *ref'd only by part names* setup! What are you getting?"

Me: "replacement SSD, laptop's finally failing"

Rando: "Yeah, I totally get you, I hate that. How old is it? Hopefully you got a couple years outta it?"

Me: "over 7yrs old."
Rando: "Wow! Mustve not used it too much, still that's pretty long."

Me: "Actually, it's been my primary device, heavily used, as I'm a dev. I just know what/when to use SSD vs the HDD."

Rando: "Duuude, that's awesome!...wait...why haven't you just bought a new laptop yet?"

Me: "I'm not for hardware abuse or burning money"

I was quickly reminded why I tend to avoid typical consumer tech stores.

Anybody ever try Best Family or Betatesters.io? On the dev or consumer side?

Job review time,
(just a random pick from the a list).
---
"Engineering Lead"
Translation: "Chief Calculator Officer"

"Anyone can design or spec a product, get it manufactured overseas and get it to market. But will it be good? Will people buy it?"
Translation: "We're looking for a miracle"

"Take on a top notch team that is going places in Electronics, R&D and advanced product development."
Translation: "Professional Excel engineer wanted"

"This company is a little-known success story that has been operating for over X years, making mission-critical electronic equipment for use by consumers, professionals, government and industry."
Translation: "Design weapons and tamagotchis."

"Working as part of the Senior Leadership team, you will have charge of the I.P. engine and product development team spinning up new ideas and throwing them out the door."
Translation: "You're success is our success. Your failure is your failure."

"The Role
- Generate New Ideas
- Push for new products
- Drive manufacturing
- Manage a cross disciplinary team that includes Electronics, Software and Mechanical
- Project Manage new projects to completion
- Interact with marketing and sales to drive results"
Translation: "We've never hired one person to be a whole team before but we think it will work."

"On your first day, we expect:
- Strong Leadership experience and skills
- Solid Engineering Fundamentals
- Experience taking new and existing products to market
- Experience with manufacturing high-tech, mission critical equipment
- Commercial Acumen
- Bachelors in Electrical or Electronic Engineering"
Translation: "We expect you know where to hide the drugs already."

"Nice to have:
- Experience with Defense or Medical Systems
- R&D background
- MBA, B. Commerce or similar"
Translation: "By clicking on this job ad your background check is already under way."

"In return:
- A loyal and oustanding team will be there to support you
- Extremely knowledgeable experts to guide you
- Incredibly smart founders to mentor you
- The opportunity to work on a real product
- Extremely generous salary package"
Translation: "Our last dev has removed the Warrant Canary. Can you pleeease put it back?!"

I've built a number of apis consumed by internal devs. Then there's one which I consumed in a mobile client–smoothest experience ever. I dogfed myself and empathised with any blind spot or skirmish that would have arisen if there was an external body

The ones consumed by others always end in tears and loggerheads. There was one with this girl who called me names and turned my relationship sour with the guys who contracted me. Our Altercation culminated in her hooking me, going as far as deleting personal media shared. That was my darkest hour supporting an api. Well, it started with her grumpy over broken endpoints, which I maintain were not that many

I wasn't an amateur dev at the time: I used conventions mastered post-suphle. Code was backed by automated tests and well documented. Now that I think of it, our earliest, innocuous argument was brought about by her incompetence. She didn't know some rudimentary stuff like how to build payloads or format to send to an api. Funny enough, the lead who contracted us both strongly vouched for her cuz they once worked together. He claimed she was no noob so I must be the faulty one

I'm about to release another api now. I've had all the time in the world to build it to production standard. Over 200 tests, all passing. In my head, I'm thinking, what could go wrong? Stakeholder introduced a feature breaking fundamental functionality. I refactored, implemented, connected tons of apis stubbed out in tests. Painstakingly began to fix broken tests to both fit integrated api behaviour and ensure system integrity is intact. Shit, software engineering is arduous. This is best case scenario unlike front end web or mobile where there is an unfixable bug or a ui requirement stumping you for literal days

Anyway atp I believe I've done my homework. The only thing that would likely do me in are those damned apis I rely on. One malformed response or missing key is enough to undo my meticulous efforts. I strongly hope not to have a huge fallout with the front end dev and the numerous third party consumers we're expecting

As an aside, On a different project entirely piggybacking off external apis, I'm supposed to write tests to verify their status. I wonder whether this is tenable or a waste of effort. But on paper, it's more reliable than building a postman collection and sending them from there