cptnbob

5 ms·

1.
by cptnbob 11y ago
Ironically this happened to me due to a card expiry fuck up.
2.
by cptnbob 11y ago
Too much vendor lock in. Will keep my VMs thanks.
3.
by cptnbob 11y ago
These are possibly great but much like my foray into DVORAK layout, there's something to be said for consistency of layout. You just sit down and use it if it's the same as everyone else's. No embarrassing prodding and arguin
4.
by cptnbob 11y ago
Yes. I think you've just been through a couple of cycles now like myself. Cynicism comes from watching the last disaster unfold :)
5.
by cptnbob 11y ago
That's just embedded systems that have always been there though isn't it? Someone just stuck a marketing label on it.
6.
by cptnbob 11y ago
Does it call 999/911 when it pours boiling water in your lap :)
7.
by cptnbob 11y ago
100% this. I haven't found a genuine IoT device that is useful. They always remind me of this scene from The Fifth Element: https://youtu.be/SnzzWGcdMqY Literally ever device has dubious utility and security so far.
8.
by cptnbob 11y ago
HTML! And you get to do it once for both...
9.
by cptnbob 11y ago
It was probably limited by the SATA interface speed back then.
10.
by cptnbob 11y ago
What's even worse is that I recently jumped into asp.net 5 and tripped over three build systems and a pile of cack just trying to get it off the ground. Now msbuild as well!?! Also its not even the right tool to build .net stuff. Add t
11.
by cptnbob 11y ago
Now I can hate every moment of its existence on more than one platform! Having dealt with it for years, it's unadulterated pain and bad performance and nothing else.
12.
by cptnbob 11y ago
They paid for our modem setup so meh ;-)
13.
by cptnbob 11y ago
One of our clients still has a DOS box connected to a 14.4k modem that we have to drag EDI interchanges off. You wouldn't believe how much it cost to get a modem and POTS line installed in our DC so we could talk to it. There's a
14.
by cptnbob 11y ago
He could also separate code and configuration as per the docs but I suspect the hubris excludes bothering to read them...: http://docs.aws.amazon.com/AWSSdkDocsNET/latest/V3/Developer...
15.
by cptnbob 11y ago
1. He stored credentials in source control rather than using configuration profiles as specified in the AWS SDK documentation. 2. He pushed code to a new repository without verifying the security configuration of the created repository (gra
16.
by cptnbob 11y ago
AWS SDK for .Net supports named profiles for VS so your source check in only contains a profile name. If you hard coded your IAM or account keys or stuck them in the app.config you're simply doing it wrong. There is no excuse. It'