gw99

Oh god no I was a CCNA. IOS is horrible.

manpages aren't always that great. Unless they are on a BSD derivative...

PowerShell had some good ideas about making commands discoverable but the nuances and implementation really killed it for me.

This stuff happens all the time.

A few years back a company I was contracting for had one of their end users report a high severity security defect. Apparently he signed into the app and thought he had been hacked because a couple of large 6-figure transactions had been made.

After several hours of inconclusive investigation where even identifying the user proved difficult, this turned out to be him seeing the marketing example screens in the app store and having a panic. The app never even got installed and he never signed up for it.

The marketing screens were quickly updated to show something less impressive and with a sample data only warning...

I can never remember all the flags and syntax. Also I hate writing parsers all day which is what you really have to do with text interfaces. UIs are discoverable.

There are some compromises in the middle somewhere. I'm liking Apple Shortcuts when it fits the problem domain I am within.

I actually uninstalled instagram and shot my account yesterday because the ads were getting absolutely atrocious. Decided it was done for me. Looks like I was right.

Conversely optimism can waste resources on unworkable progress which could have been applied to workable progress. Reality is way more nuanced than single perspectives.

This smells like "I don't like how SQLite because I can't get in to the party so I'm making my own party" which is fine but don't denigrate the product or the contributors who have been doing an amazing job for a very long time.

My last one expired 20 years ago.

Historically yes. Your job is to evolve this configuration as security controls improve. It's not a fire and forget process, it's continuous improvement.

They don't really though because in the several systems I've seen configured like that, the same staff have access to all accounts. Accidental deletion and unauthorized access should not be a possibility via policy rather than isolation, because if the former isn't done then the latter will not help. If the client demands it, sure, but charge them for the inconvenience.

The main risk is hitting resource limits which is why I would and do give development teams their own account to cause mayhem in.

None of these concerns require multiple accounts. An account is a container for resources and resources do have tangible isolation between them if configured properly and properly delegated credentials should be issued to staff which are specific and limited in capability. Same with assumed roles. Same with VPC configurations.

If you didn't do that, you fucked up. Adding more accounts doesn't guarantee that you didn't fuck up.

And yes you need to open 10 tickets, even if you have enough spend to have a direct line to AWS internal staff with multiple enterprise accounts...

I disagree with this perspective. You should have multiple accounts but only if your organisation requires it for isolation or data protection reasons and only enough to perform the task.

Every other reason here is because you fucked up. You have poor architecture, poor tagging, poor VPC design, poor IAM policy and role modelling or don't know what you are doing to start with. And some of the stuff doesn't even make sense, particularly the point about EKS upgrades (I run three different versions of EKS in the same account).

There are many negative effects of multiple accounts including billing aggregation is very difficult, having to dig through several accounts worth of Cloudwatch logs, unexpected egress traffic costs and the overall complexity is much higher. If you have to switch to an org account and set up SSO you then have an administrative cost which is immense.

My favourite thing doing is spending 2 days opening support tickets in 10 different accounts to get a limit raised and then tracking the state of all the tickets and limit changes...

Yes VScode but fuck me it's still painful.

I've been through that "no code" cycle at least three times, ironically including Oracle in two of those cycles, and they always died on their ass. I suspect the same will happen again.

It's really hard to build something generic enough. MS Access was as near to it as was feasible I suspect.

Well my pet hate is that I write a lot of YAML. It's poorly structured, unreliable, nuanced, schemaless and difficult to edit reliably. I prefer XML and XSLT to this shit show. Oh and unnecessarily distributed things.

In summary, apparent simplicity that causes actual complexity is a big problem now.

Oh yes this. I wrote a timesheet system in VB4 32-bit back in the day in 4 days and rolled it out to 10,000 users. And it worked. And it stayed working for 15 years until it was replaced.

In 4 days worth of work now, I couldn't even do an evaluation of which UI tech is still going to be around in 2 years...

There is the voice of someone who has never actually been in the position of getting into an actual pit of depression over the toolchain you have to use. No joke but I was doing some work on VSTO in Visual Studio Classic a few years back and it really did me in. Every day was this unpredictable nightmare that was going to attack me over and over again. I dreaded getting up in the morning in the end and developed a reputation for being late and unreliable, which are two things that aren't my usual self. It took me a few weeks to realise it was early stages of depression.

Since then I spend a lot of time carefully evaluating tools and software before I ever consider using it or taking on work that involves it. This is to avoid the mental toil that is almost endemic in really horrible bits of software.

Quite frankly this article nails it. Software has to be comfy or it can fuck off before it hurts me.

Been there. Remember the immediate priority of work is to satisfy your personal security so that means cash. Always. Then remember it's someone else's cash. If you are an employee and it goes to shit it's not your problem. Just think of the cash building up, not the carnage, chaos and mayhem. Picture yourself as an outsider looking in and distance yourself from it as much as possible. It's not worth killing yourself with effort or concentration over someone else's shit show.

With that in mind, write down what you want out of your life and job and set some simple easy to achieve short term objectives. They might be health or learning related. Then go out and do them. This will build motivation to actually deal with the issue which is the job sucks and you need to change it. Write down criteria for your new job and spend your time finding it. Don't just jump on the first thing.

It's really important to get yourself together mentally before you jump ship though because it's very easy to end up in exactly the same situation or worse if you make a rash uncalculated decision.

I've seen it working for schools with 5000+ account so it'll go well past 100 users. Not sure I'd want to depend on Google though.

NetIQ eDirectory tends to be the other big one. Although I am seeing a rise in companies not having an SSO solution recently at all. In fact some of the SMEs I've seen recently are running most of their stuff entirely via basic Microsoft O365 accounts or iCloud.

I had problems with Windows Defender finding a false positive in the output of a product I was working on. This was an EV code signed MSI package with signed exe. This eventually inflamed SmartScreen and despite getting the thing sorted as a false positive by the AV guys it took 3 months for it to stop being flagged.

After working on Microsoft dev for ~20 years, 2019 was the last thing I touched. I handed everything else over and moved on. I will NEVER deal with that company again. Nothing but fucking shit for that entire time. The grass /is/ greener on the other side.

I think the best thing is wait 5 years and see if they are going to shitcan it or not...

It's horrible. After futzing with it for a year or two for trivial test rig and automation stuff I switched to avr-gcc and avr-libc toolchains and just used vim and makefiles now.

Oh she deserved it. And the HP windows 10 laptop with 64Gb eMMC storage.

Yeah good luck with that. I did the same. Then all the streaming devices stopped working suddenly. Turns out that there was suddenly an HDCP compatibility issue which obsoleted the TV instantly.

You can crack the things open and unplug the wireless module usually.

If the TV stops working then, well you solved the problem anyway :)

I left my Tizen based Samsung with my ex wife when we got divorced. This was a subtle troll because I am finally free of the fucking thing and she's not.

The last decade of ownership has been hell. Slow laggy equipment, HDCP problems, working but forcibly obsoleted hardware, bugs galore and ads stuffed in your face.

I now no longer own a television and will never own one again.

Yes - I should have clarified that. The extra flux thing is the problem :)

Yep. To be honest a lot of stuff we didn't clean flux off professionally. Anything which was solvent safe would be soldered on, the board cleaned, then anything not solvent safe would be soldered on and it'd be left.

It's the .154" Molex stuff that tends to melt after 20 years spontaneously. Not sure what plating they use bit it turns into a power dissipating resistor after a bit which is not good when you're shoving a few amps through it.

Oh just reading that hurts!