60 karma · joined September 11, 2015
But it is mighty difficult to do this kind of niche work because developers will then have to spend an inordinate amount of time acquiring relevant domain knowledge to implement these niche solutions. Hard earned knowledge that will be useless after the project is complete. And the effort of acquiring this domain knowledge will often be under-appreciated and underpaid, cause it is very very difficult to estimate this effort no matter how good an AI have you.
Designers are often pushed into the rear end of the process in every sort of consumer product development (including software development). It is no wonder therefore that we end up with not only ugly but often unusable products. Big opportunities all around for a company that brings good design and better designers to the forefront of product development.
But it is just too damn hard for most people to let go of their ego where design is concerned. The whole design thing looks so intuitive and apparent right from the start that we can't believe we can't do it all ourselves, and, not only that, do it better that everybody else.
This. From the interview[1]. I think this is the most important takeaway for people building software. An inherent assumption here is that the deeper layers in the software undergo less changes and iterations compared to the outer layers. This may not always be the case, but it often is.
I think we can have the best of both worlds – enjoy our whiskey and discuss philosophy too :) I think there is a future for a social network that can slow things down a little, maybe also summarize, organize and filter an apparently disparate group of things, allowing the user enough time to digest and process the information before moving ahead in leisure.
I think that the current complaints about age-discrimination, apparent and false though they may be, indicate a misguided but passing phase that the industry is going through. People are hedging with trivial ideas and products, hoping they will stick. These guys built a CAD product on the cloud called Onshape, check out their engineering team - https://www.onshape.com/team
Hell, I am ready to join their efforts, if only they would have a grumpy old guy like me on the team :)
Also software engineering sounds unglamorous today and research in the field seems to have stalled. And therefore the craving for the simplicity of the Unix philosophy. Not that the Unix way of working actually solves the problems posed by software complexity, it just asks us to avoid complexity.
It seems plausible that the tech industry, innovation-wise, is actually in a rut where companies are forced to cut costs and survive by hiring young people whom they have to pay less. The changes happening in the industry today are of a fickle and shallow kind, not fundamental and lasting. And in an evolution-like process the older amongst us, who are the only ones with enough experience to really innovate, are being driven out of the ecosystem and forced to disrupt an industry going stale.
I also think that this is a subjective article, which, while it tries to list down the differences between good and bad traits of a product manager, fails to strongly separate the bad traits from the good ones by using vague management speak, and in general ends up making product managers feel goody goody about just being product managers.
I am in my mid-thirties though and I can't recollect having run more than a mile before in my life. Maybe I will get used to this high and stop feeling the difference. Maybe I am feeling the kick because it is novel to me. But yes, it is nothing like the high you get from smoking marijuana :)
Why wasn't handwriting recognition a big success?