They're borrowing techniques from game developers, it's really just the illusion of choice and both will cancel it anyway.

It's not like this is new people trying to remove the flag, it's the same folks who have been trying and they got a lever. Then every gutless company in the country decided to get in on the action. But let's be very honest, when you lose the war the battle flag comes down. When you hoist the thing back up as a result of the civil rights campaigns you're sending a very clear message. One that has not one damn thing to do with heritage.

What if they both buy drinks? I've seen the margin on fountain drinks.

Tell then how much better data will save them. Time spent updating and manipulating crap data costs money after all and Hoovers is about as good as I've ever gotten.

Would be kind of fun to have a trained attack fridge that didn't involve me getting pelted with frozen veggies.

Elon says fear it, I don't flinch. Google says don't fear it and I want to hide under my chair. I'm going to say these people don't have the reputations they want to.

Easily the best way to get honest feedback when they forget you're there though. Part of me wants to be a coder cog in the big machine just to see what it feels like when you aren't responsible for the entire process. I'm guessing it's just soul crushing in a different way.

So long as it isn't a book with swaths of code in it you're expected to copy(which generally fits better if you flip it over to landscape) I'd say it's far better. I've bought what is easily 40 lbs worth the programming books on mine, I carry the lot of it in the kindle and have it all available more or less all the time. It's also slowed the growth of my recreational reading shelf considerably, which is good as the shelf is beginning to consume all of the area around it. Still reading, just not getting everything hard back. My one piece of advice with it, turn the text size as small as you can manage. Odds are it'll still be bigger than a trade paper back. If that is still huge after changing the settings on the kindle, look into some of the unpack/repack software for e-books. I've had to neuter some remarkably poor publisher decisions in terms of font size more than once. That helped me a great deal with a few of the programing books, turning the page every half sentence isn't what I was looking for. Edit: Lies, I have more than one thing of advice. Drop the brightness to the minimum you're comfortable with and turn airplane mode on. It'll save battery and I've found the less bright backing easier on my eyes, but it really depends on the light around me at the time.

Beware of TVs with freaking boot times. Little has made me happier about buying my cheapo TV than watching my friends massive beast take 30 seconds plus to turn on.

This is all a very good reason to work on your sales pitch if you're a small team of internal developers. Sometimes being able to sell software to the people who hired you to write it will save your job, other times just make your job more livable. Custom software is only worth what they think it is until you show them otherwise.

I had this argument while I was still in college. A team member had decided the entire major was worthless because we had to use prescribed solutions to everything. Apparently having missed the point that these general solutions can (and should be) modified to fit a situation, and the point of our major was identifying when a pattern would be useful and exactly how to implement it in that situation to best benefit the software and our own sanity. I mean hell, look at adaptor. It's a stopgap solution to keep you from having to re-write libraries and nothing more. This isn't a sacred text it's a few useful ideas. But yeah, doesn't stop people from treating it like their personal bible.

Even the fire's have pretty good battery life(kill the brightness a bit and turn on airplane mode). Beats having to move the massive programming books around, cheaper too. I do kinda miss having paper backs for fiction, but I'm out of shelf space for them anyway.

Oh, well, that's the media. Not much to do about that other than laugh and see if they have a tech article that's more inaccurate than their legal ones.

The airbag should have deployed as required by law and it didn't. It may have saved the lives lost and possibly reduced injury in other accidents. The point isn't how many people died, it's that the company knew a required feature didn't work and did nothing to fix it. That's what they'll be held liable for.

They're guilty of not fixing a known issue with a required component intended to reduce the number of fatalities from accidents. At the very least they're down for knowing shoddy compliance with airbag laws. I'd be really surprised if they were actually found guilty of the deaths, and far more likely those deaths will be used as justification for inflating the penalties assessed for failure to comply with the law as it's unknowable how many are their fault. Still, if you make something and your safety features don't work you're going to get a civil suit even if you didn't know about it. If you know about it you deserve every last bit of it.

I'll second this, just be sure to keep up on your security certificates or it might take a small war to get access back. The guys over at Bundle of Holding ran into that.

It's also possible the cats are simply a bunch of wusses. I had a complete wuss cat, he once ran away from a mouse trapped under a colander. Then I wound up with a few half feral cats, those animals knew how to tear up a mouse, and the walls, and the insulation, and the carpeting... given the choice I would have taken the rat problem.

I doubt I'm allowed to speak to exact results of such a thing, but I'd suggest the number of positive results are an extremely round number.

Sounds like a "Bring me solutions not problems" kind of guy. The Graphic artist has given him a solution, you've given him problems. So yeah, he likes whatever foul creation was handed to him because it's at least something. Take the graphic designer, go talk to some end users on just what the process they go through is. If the designer's approach really is how they work swallow some pride and squeeze the code out, if it isn't then start designing the work flow that needs to be produced and have the designer put together some mock screens for it. Run that past the users, if they like it run with it, if they hate it burn it and start over, if they have a few suggestions integrate them. If there's a lot of change do it all again, but one way or another find a way to make progress that gives the owner something to look at rather than questions to answer. Trying to get answers from such people is like pulling teeth, it's easier to get them to tell you what they do when they run through the process than get them to tell you want they want the process to be. But, if you present them with something that requires less screwing around in their process they'll respond well. Then of course you have to dig out the edge cases no one mentioned, but at least that's a later problem.

There's a god awful number of ways to get around such things and people get really annoyed when you block what they use to get around their job's IT security.