Schematics for everything
Schematics for everything
Agreed. And while people might complain that it makes "buckethead programming" easier, the thing that's not stated is that it also makes it easier for good experienced programmers, which is a significantly better gain. After all, most of those "buckethead" newbies will eventually stop being such.
Fresno used to be worse, but North Fresno especially is actually nice. Close to the mountains for skiing, and the people are a lot nicer than in most big cities in California.
Well, he did give a reason right there. Rather than slinging mud at the NASCAR crowd, he should be trying to anchor his message in a way that gets them excited about the scientific aspects of it.
I feel like Nye is generally really good at doing the latter, and this was just an unfortunate break in his cool. It can't be easy staying calm when you're debating morons. Everyone's got a breaking point.
>I'm in SF working in tech (of course) and I've been thinking about moving south... Irvine seems like a pretty decent destination.
Or you could move east. Fresno is very affordable, and in the last five years has really started building a good tech scene. Lots of companies, ranging from startups to incubators to established firms like Decipher.
It sounds weird to say, but there really is a tech renaissance going on in Fresno these days.
But, there are a lot of low skill programmers and sysadmins out there who lean on these tools way too much.
The low-skill people would have been low-skill regardless. Tools do not make the person, they only help them to be slightly more useful. People said the same thing about IDEs ruining programmers, but I think they've shown to be a net positive.
Many closed questions have what I'd call "false nuance" --- the person did not boil the question down to what is actually breaking. Their questions are scattered -- something like "I'm doing X and Y using Z library, and it doesn't work". The experts reading them can identify the problem as nothing to do with X, only a tiny bit of Y, and not in anything related to Z. They know what should have been asked, and that it's an obvious duplicate had the problem been reduced.
I don't think anyone would argue that this is helpful to the person asking the question. The real question is how far should someone go to answer a lazily written question. Especially with SO's gamification shtick, people are less likely to want to deal with questions that waste their time.
Do questions with merit get closed occasionally? Definitely. I try to reopen them when they do. But far more often than not, closed questions really should stay that way. There's this great old document How To Ask Questions The Smart Way . While StackOverflow is significantly more lax than it would have them be, it's still good reading for anyone deciding to post.
Release now patch later give CEO big bonus for laying off QA (we have end users that pay to due that)
I've talked with enough folks in QA to know that in the majority of cases all these game-breaking bugs are known and reported by QA prior to a game's release. The problem is marketing has promised a specific date and they're damned well going to meet it even if it means putting out a day-zero patch and dozens of patches over the next several weeks.
Knowing this is why I'd be perfectly okay having reviewers down-rate a game for a buggy release. It's the only way we'll be able to show them this toxic behavior isn't what we want.
>The Intel of 2015 still has a very solid competitor eating into its profits: the Intel of 2010-13. I am typing this on a 2600K I bought in 2011, and I have no intention of upgrading any time soon. I have went from 8 GB of RAM to 16 GB, from a 128 GB SSD to a 480 GB SSD, and I upgraded my monitor setup. But my desktop processor is still more than twice as fast as my 4300U work laptop, which I never worry about being slow. I wouldn't be that surprised if this processor lasts me until 2020, unless it stops working before then.
Ditto. Last week, a nagging voice in the back of my head told me it couldn't be possible for my 2600K to still be a viable CPU and to look into upgrading. After checking out CPU benchmarks for the latest round of CPUs, I was sort of surprised to see there not being any significant improvement. I'll probably wait another generation or two before my next CPU upgrade.
No kidding. The thing continually suggests that Linux is insecure on all number of ways (none are mentioned specifically), and that Linus is indifferent toward security. It has this completely useless statement to try to create a false association between Linux and the Ashley Madison hack:
Versions of Linux have proved vulnerable to serious bugs in recent years. AshleyMadison.com, the Web site that facilitates extramarital affairs and suffered an embarrassing data breach in July, was reportedly running Linux on its servers, as do many companies. Those problems did not involve the kernel itself,...
>"So", you ask, "what does he think of that?" I'm glad you asked!
I just went to one of his talks at the end of September. He has nothing against working with other people, per se, in fact he spoke repeatedly about needing to match people of different strengths together. Such as on the invention of the Disk ][, he partnered with a person who was better at OS stuff than himself (since he wasn't a wizard in that area), and together they got the thing built in record time (why? because Woz says they'd bribed him with a Vegas trip if he could get it to work) and drastically cheaper than any disk drive done before.
He also said Steve Jobs was invaluable in the success of Apple, despite him having (this is almost a direct quote) no technical skills, no real education, and never having achieved anything technical in nature in his life (all of his projects were failures). But Woz said that Jobs knew how to look at things from a different perspective, even very simple things like reordering the colors on the Apple logo so that they were more balanced (ever notice it's not in ROYGBIV order?) or knowing how to market and sell the product and make people believe in it. Woz never wanted to have anything to do with that world, so he found the partnership very valuable. Even before founding Apple, Jobs would come down from Oregon a couple times a year and see what Woz had invented, and go around the country selling the products.
What you quoted was arguing against design by committee which is a very different thing.
>He made the Apple I and II alone. Not in teams.
Have you ever read the story of the Disk II? (http://apple2history.org/history/ah05/) Woz used his brains to design a disk drive radically simpler and cheaper than how it had ever been done before. But it wasn't just him. He worked with Randy Wigginton night and day to get it worked for CES '78.
So no Apple Computer then? All right.
And what makes you think it's antithetical to being a team player? I used to work for a contractor where minor practical jokes by everyone on the team all the time. It made work more enjoyable, and kept our mental skills sharp.
You have a massage (from the Swedish prime minister).