cheery

Shut up Microsoft shill.

Most people do not even have a clue about which operating system their phone has. And they do not care. Just like they do not do with PC either.

If Windows Phone doesn't interest anyone. It is because they were unable to fit a niche. It is because their phone is a disaster. The operating system is irrelevant for most of phone users.

You know your text annoys me? Although the author is off the point, you continue the trend, and you're exactly as much correct as the author is.

Lisp syntax is just a notation for lists. Lisp implementations process those lists.

Any syntax which is a notation for something generic quite much makes sure that most changes into the compiler does not ripple into the parser. They make it easier to experiment with your compiler design because you're not changing parsing rules all the time. And changing parser code tends to be error prone and take lot of time, even when you're using parser generators.

What did Ballmer actually state there? I barely could find any message from that wall of nice words.

How the reorganization is going to differ from the earlier one?

I've found open source so liberating that I couldn't even consider closing down my source ever! For a while, for me, it's been morally wrong to close source code or rely on sources that's not within your reach.

"why should I compromise my own ability to license this and make some money from it?" It's the same reasons you don't do slaves anymore. This guy needs to figure out better business models because the ones she's trying to do are obsoleted.

Also it's not wonder that her Kickstarter failed, it sucked very hard. Big TL;DR with no marketting material that would motivate people to pick on it. Most of people who saw that thing probably had no idea what they could do with her project.

They contain different points I noted, in the pace I discovered them. I can do as many posts as I want, do I?

Or did you mean that I can EDIT the single post, until it contains everything I want to tell? Sorry. I did not figure that out until now.

Quick fix can be permanent fix. Those adjectives do not exclude each other out.

I think this article's biggest problem is that he's using running phrases too much, that are correct but without meaning: "If you skip work, you have to work more later" Obviously.

Also anything can be taken as art, even things not made by human! "Think of programming as an art". What does he mean?

What's the point of having warnings in the first place, if you treat them as errors?

Also what's the point of having errors that prevent you from executing the rest of program? One error in one module shouldn't prevent huge suite from compiling.

If you stumble upon a new problem that's unknown to you, you should ALWAYS search what others have done. Only after that you'll try yourself if necessary, knowing the mistakes others made. Good programmers are lazy.

You won't challenge your mind any more by not searching, that way you're just being stupid. Besides, it's much easier to create original works if you know what's original and what's not. This is why you should be studying other's work before you do your own.

I've been always better off by starting with an empty file. It lets me concentrate on the problem I am solving, with no fringes or bells that belong to the finished product. Also starting from scratch is great if you're stuck. If something prevents this behavior, you're better off by tossing it away.

I think he should rather state to think clearly. You should always think for yourself about using a library. Does it fit your needs? Use it. If it doesn't, do not use it. You will not save time or your mind by using something that doesn't fit.

Copy-pasting code without understanding is functionally same as importing large libraries or linking to them. You'll have same problems even if you didn't copy anything! This is why good programmers review code and prefer open source.

His advice about copying is entirely wrong, because even if you don't understand some code, it can still be okay to use it in your project.

The biggest problem with copying is that you easily get more lines of code you have to maintain. This is especially bad if you copy large chunk of code, which may improve later. If that happen you have to do the copying again to get the improvements. Link or import the code you need instead!

Pick a fatal design flaw in popular product, such as fragile display in iPhone. Build up a repair service around that flaw.

If I invented a similar get-rich-quick-scheme I might also grin like a trollface and that guy in the video.

What.. Are these government sites? Those do not look like such as they are too clean and positive. Are you sure they're just not a victim of very stylish hacker?