731 karma · joined April 19, 2013
(and I'm not writing trivial apps…)
The distinction has to be made between what is lawful and what is moral. The law is a system that we all have to comply to (which may or may not be perceived as moral), morals are subjective and built on experience, environment, etc. Laws are often made with current/major moral views in mind.
Tax evasion is clearly perceived as not moral, but it's lawful. We cannot expect companies (or individuals) to obey moral rules, since it's kinda unsolvable (morals being subjective). On the other hand, we can expect them to obey law.
Again, focusing on companies in this case is pointless and unproductive, no matter how shocking it is. Governments like to criticize tax evasion, but they are the only ones who could do something about it. We have to go after them.
But I agree, lately I don't like what they do. My favorite is still the iPhone 5.
I agree that a lot of people don't make the distinction between rails and ruby. I had interns who where quite surprised you could use ruby without rails, and that "it's actually a complete language!". Ruby on its own is charming indeed. Rails gets the job done: few other tools enable you to finish a functional MVP in a day or two. But if you start to add gems for everything it just becomes a pain in the ass.
edit: I was f*cking mad when they added coffeescript. fortunately it's simple to disable (just removing the gem and changing a setting for the file generators)
As a music app developer myself, I can say that UI design for music software is a completely different beast than "general" UI design.
Shows how the press is extremely focused on buzz. Doom predictions sell.
-- my former boss
Valve did an amazing job at building their reputation (by doing things the right way.) Very few can do DRM without pissing off people.
Yes it can be a pain to write. But I prefer the pain of making the compiler happy than the pain of debugging a weird segfault.
I've seen it countless times, at this point "plain emails work better" is an elephant in the room.
Specifically, that the outcome of a desire for freedom is democracy. It's not freedom itself. I still stand with my point, both should not be conflated at the risk of being blind to the shortcomings democracy could have.
Democracy can have shortcomings and still be the best system out there, but being aware of them (questioning freedom vs democracy is one way) prevents our systems from drifting away.
- Freedom and democracy are different things, if some people think democracy isn't that important, it does not mean they do not value freedom.
- Maybe the millenials are "not open to diverse opinions", but maybe they're just sick of bullshit. "Free Speech" can be interpreted in different ways (and each country in the world does that).
Documentation should not be a matter of "every function has a docstring", a description of the architecture is always useful.
They are also a joy to design/implement* and doing it really changes how you think about programming.
* http://hashmal.github.io/shirka/ my personnal attempt at designing such a language. warning: very old, dirty, buggy code.
(that's not a complaint)
In many cases there is an inherent complexity to a product, and it warrants some learning curve. Removing the need for documentation often removes power and depth.
Funnily, now that many products are like this, the opposite trend is surfacing, and in some niches you have customers who love reading manuals. It becomes part of the user experience.