Yep, that's the flip side. It helps fight depression, but it also has an addictive side to it. Fortunately it's really not as time consuming as you'd think, but taking a whole week off is almost out of the question
54 karma · joined July 3, 2014
Yep, that's the flip side. It helps fight depression, but it also has an addictive side to it. Fortunately it's really not as time consuming as you'd think, but taking a whole week off is almost out of the question
Professional programming is about managing complexity. It's about putting thousands of man-hours into one single project with a dozen of different people without anyone's head exploding.
Light-table could have potentially been a huge help in the constant battle with managing complexity.. It's an area that has need some serious development (virtually nothing substantial has been added to IDEs in the past decade). But instead you're going to create a beginner friendly monster.
This is the opposite of progress
In VS13 the R-Click -> Go to Definition interface is OKay... but it definitely could be better
Most programming concepts are really about code organization and not expressiveness or the ability to express an algorithm clearly.
Object oriented programming only really starts to make sense when you are working on something that will take thousands of man-hours. If you are working alone, or on a small project is can be completely irrelevant.
The work flow you are describing is what MATLAB guys do. It's an absolute nightmare once the project gets too large. It is however very fast an flexible for prototyping.
"The function that is least likely to cause a problem is one that doesn't exist, which is the benefit of inlining it."
That's the equivalent of saying "the faster you drive the safer you are b/c you're spending less time in danger"
You'll just end up with larger monster functions that are harder to manage. "Method C" will always be a disaster for code organization b/c your commented off "MinorFunctions" will start to bleed into each other when the interface isn't well defined.
" For instance, having one check in the player think code for health <= 0 && !killed is almost certain to spawn less bugs than having KillPlayer() called in 20 different places"
I don't completely get his example, but I see what he's saying about state and bugs that arise from that. You call a method 20 times and it has an non obvious assumption about state that can crop up at a later point - and it can be hard to track down. However the flip side is that when you do track it down, you will fix several bugs you didn't even know about.
The alternative of rewriting or reengineering the same solution each time is simply awful and you'll screw up way more often
As an aside, I had a professor from the MS Research lab in Santa Barbara who was a complete moron. Seemed like he was some kind of middle manager at MS and then went to Research for an early semi-retirement
Rust is inherently memory safe - however in practical terms this isn't important for most applications. If you are writing security critical applications Rust will provide you with some very important guarantees (ie. there are certain mistakes which are inherently not possible in the language). C++ doesn't really guarantee anything and if you're an idiot you can shoot yourself in the face. However in practical terms memory management in C++11 is very straightforwards and C++11 compliant code (ie. using the STL and not writing it like C) is very safe and clean. You're not mucking with raw pointers anymore
The main issue I see is that Rust is still in early development. It may or may not get "big" in the coming years. And library support is ... lacking
In contrast C++ has the STL and boost and every library under the sun. I haven't working with a lot of other languages extensively, but I've never seen anything as clean, robust and thorough as the STL and boost. C++ will remain relevant for a long long time. If Rust takes off in a big way, you'll be well positioned to jump ship.
They are focusing on nuclear for reasons of energy diversification and independence. (look at how Russia has Germany by the balls right now)
>The claim that one can own an idea is silly on its face
You do realize that the la-la land you want to live in doesn't preclude the ownership of ideas. Trade secrets will always exist and there is no practical way to prevent their existence.
Not only do patents allow innovations to be shared - but it also opens up the limited-time monopolistic advantage to other industries. It's easy for Google to have a secret algorithm on their servers, or for KFC to have a secret recipe - but it's harder to have a secret algo in a DLL, or a secret engine in a car.
In your world, hilariously, in-house server side software development would be significantly more profitable than client side software development.
I think you're missing the point. If we acknowledge that there are differences then we can come to terms with the fact statistically men will always be more likely to be CEOs - that doesn't mean we should stop fighting sexism or whatever other issues we have culturally producing prejudice - but it does mean that we may not need to strive for some kind of ... statistical parity.
In another comment you say:
> What I am saying is that women and men are equally capable at being great business leaders
You have no way of knowing that. That's a pure guess on your part. We know that women and men have different brains on the biological and chemical level so, all things being equal, surely it would lead to a least SOME difference statistically on which gender ends up being CEO. The question after that is of degree and does our current gender ratio predominantly represent a biological or cultural phenomena.
Since we historically have a lot of different cultures, and all seem to produce significantly more male leaders than females on, I'd say the biological argument has a lot of weight. I could be wrong!
If I had it my way, I'd work half time programming and half time working a public facing job.
Most people just live boring normal middle class lives. I'm not denying that there is a problem, but I think it's not necessarily a statement about Japanese society as a whole. It's like if goth kids started slashing their wrists in large numbers. It might be a reflection of US society as a whole, or it might be a toxic subculture.
I think people are in some kind of serious denial about the drastic increase in bandwidth being demanded by customers.
I don't think Sprint's solution is healthy for the state of the internet, but I do think something will have to change.
I personally don't use any high bandwidth services. I don't watch Netflicks, or a lot of Youtube - and yet I'm stuck with higher and higher internet bills and I have to subsidize other people's use of the internet. Frankly, that's ridiculous.
Ultimately I think the system will have to revert to the $/Gb system we used to have. If we all reverted back to that, I think you'd see some very competitive pricing.
However the selective traffic stuff.. that's a bit scary. I don't think they should be allowed to look at our traffic in the first place. I understand you need to look at the packets to be able to route them, but anything past that just seems like it should be illegal.
The Model3 is their chance to break out of the luxury market and the Leaf is going to squeeze them really hard from the low end.
I think at the point, the main thing setting them apart is the Supercharger network. The financial viability of that endeavor is a bit unknown.. but if it translates into significant car sales, then it may pay off.
The Model S is exceptional in that you can pay a ton of money and get an electric car with a very respectable range. But that doesn't really scale down when - like the article points out - most of the cost is in the battery.