setq

29 ms·

91.
by setq 10y ago
I agree with what you've said but IMHO is a dishonest way of living. I'd rather be poor than a suck up.
92.
by setq 10y ago
It took me about ten years to calm down :)
93.
by setq 10y ago
This sort of stuff fucks me off. I got into trouble at university when I was running a CAD session on X (Cadence VLSI design FTW, not). Some asshat had telnetted in and was trying to brute force root because it was a faster machine than the
94.
by setq 10y ago
Three children in, yes definitely.
95.
by setq 10y ago
Had the same. The technical director of the company I worked for was saying that it was all going to be commercial windows and x86 in 2020. I said unix, open source and ARM. I think we had a £20 bet on it.
96.
by setq 10y ago
I use putty. Haven't found a compelling reason to use anything else yet.
97.
by setq 10y ago
This is what I use Windows for. It's an SSH terminal that has a web browser and plays music (via groove which is actually quite good)
98.
by setq 10y ago
I don't buy it. As a formerly epic consumer of Microsoft products, I can't say I've actually seen ANY change other than a new fluffy marketing facade and a figurehead who appears to be able to walk on water unquestioned simpl
99.
by setq 10y ago
I'm completely screwed then. Surprisingly our hands don't suddenly fall off when we get to 32 :)
100.
by setq 10y ago
You are correct. Some of them are even swapping tapes daily blissfully unaware that the backup software failed 9 months ago and is just dumping an error in the event log, the UPS batteries are bulging about to burst, a squirrel has been wor
101.
by setq 10y ago
No. Use ansible and run simultaneous infrastructure targets in rackspace on openstack and on AWS. Scale one up if the other shits a brick.
102.
by setq 10y ago
This is merely an example. There are numerous other things that can go wrong which are irrecoverable.
103.
by setq 10y ago
This. OpenStack seems to fit that role well.
104.
by setq 10y ago
I'd burn it all and whistleblow the source.
105.
by setq 10y ago
I explicitly mean IaaS not bare metal as the target. IaaS is portable. PaaS is not. I wouldn't have an ops team.
106.
by setq 10y ago
It is expensive. Unless your product makes a ton of cash.
107.
by setq 10y ago
I've build a couple of startups and sold out, worked for a couple of well known ones as early employees and now reside in an architecture position. This magical free time never appears, particularly when your business is suddenly retur
108.
by setq 10y ago
Avoiding this is the best approach. Buy two cages in different DCs :)
109.
by setq 10y ago
Agree here. I recently implemented a small query language DSL uaing Antlr and I regret not writing my own lexer and parser. It's difficult to bend a framework like Antlr into a useable state if you hit an edge case or require unusual l
110.
by setq 10y ago
Exactly. Also it reduces portability risk. Consider if you implement SQS and SES using their native APIs then Amazon shaft you, where do you go? The answer is rewriting everything as AMQP and basic SMTP services, which until you're don
111.
by setq 10y ago
It's not. If any of the big three entirely disappeared there wouldn't be a tear shed. It'd be an inconvenience at most and people would suddenly be reminded about portability and lock in. At a microscopic level it's pret
112.
by setq 10y ago
Had this problem before. If you send something expensive, film yourself putting it in the box, write the serial numbers down, send it recorded or signed for delivery always, withdraw EVERYTHING from your paypal account instantly into your b
113.
by setq 10y ago
There's CPU throttled and then there's the 'completely undocumented useless wall of pain' I find with T2 instances which is a bit after that. A throttled box is usually just about responsive but there is a point of no re
114.
by setq 10y ago
Does the lightsail instances have a hard CPU credit limit as well? The "let's turn into a snail in the middle of a kernel update and shaft everything" one.
115.
by setq 10y ago
What's in your $PSVersionTable? I'm doing this on windows 2008 server.
116.
by setq 10y ago
It doesn't work for large files. Try iwr with outfile on a 16Gb file on a 4/8Gb machine. Knowing all the edge cases, exceptions and places where reality breaks down is the problem. Where software should indeed work with the princi
117.
by setq 10y ago
This is in line with my experiences with powershell (or powershit as we refer to it). The canonical example of the complete failure and total friction is in the simple case of obtaining a file from a web server and sticking it on disk. This
118.
by setq 10y ago
This. I find DDG is the vim of search engines. Small learning curve but immensely powerful.
119.
by setq 10y ago
This is a terrible strategy for technology early adopters and evaluators though. It's once burned, twice shy for a lot of people and Microsoft have burned a lot of people in the last few years by completely yanking the rug from under &
120.
by setq 10y ago
I'm still surprised at how many things they can completely fuck up in one go. That is increasing.

More ›