31 karma · joined January 18, 2011
However, the extending shipping time as a punishment part from amazon is not.
(Disclaimer: i work for publisher and a writer myself)
(Edit:typo)
USPTO officials should have the power to inquire pattern applicants about their pattern until complete understanding, not to work alone and try to understand it by them self. It is hard to understand something technical, and it is utmost difficult to try understanding technical stuff with only 'lawyer' language as interface.
The fact is, many of this pattern applicant try to hide their 'Obviousness' of their pattern behind lawyered up and jargon filled language that proven to be hard to understand and open to misinterpretation.
I prefer to be passionate about tools on hobby project, understand the real implications and usage before commit to use it in project on the job.
There are two component here: 1) 10000 hours and 2) deliberate practice.
What op present us are "you can ditch 10000 hours because deliberate practice is enough" but when you go through the article it shows that all test subject were trained for very narrow set of mastery for short time period (bean bag tossing, microsurgey) or very wide set of mastery for long period of time (football play)
you need to consult a web developer that you trust for these issue.
- Lean startup (eric ries): big picture/map for startup
- Product/Market fit: you have found a scalable business model
- Bmc: tool to quickly mockup a business model and its feasibilty
- Job to be done: tool to understand customer problem space systematically.
Now, pick the right tool for the right job.
i genuinely thought that the article should do justice by putting the same effort as jeresig post. Yeah OP argument that "CEO job is not only coding" is not wrong but i expect OP will argue that "code is not the onpy thing developer like jeresig do" based on the headline.
Mr Client thought making software is as easy as typing onto computer. It magically done exactly how he think the software should be done, with only limited time.
And limited budget too.
And open to changes too, while still adhere to the same timeline.
The argument is good and entails new perspective on this challenge but further refinement is needed to move closer to solution. Reasons aplenty but solutions seems not.
What frustrate developers/engineers are their code changes need to pass the test immediately. The consequences is immediate. Compare it to design consequences, it seems like an eternity, especially if the design changes never have any test/measure to get passed.
Designer can blame developers when dev cant code their design which is so delightful the sales will improve. But developers cannot blame designer when the sales does not come through from the changes. Sales manager do.
There is test for design and it was called 'split testing'. Unfortunately it is marketers/sales job to come up with the test, not designers.
By these rules, designers should be in sales team instead of product team!
Noted!
Managing ego and heart is harder than managing a project i think.
IMagine the huge sum of money which is different pool than tax money.
Large pool of money will attract attention and political pressure from dishonest individual in power.
And, when the agency is only focusing its effort in collecting the alms instead of distributing it to the needy, then the pool will only get bigger, and be the source of tension within society rather than 'peace of mind' force.
so far there is no 'huge' scandal erupt yet. The key terms here is 'yet'.
And if there is large subset of society not honest and try to pose as the needy to receive the alms, then the system is screwed.
ps: i am muslim and i pay alms every year. But sadden by the poor distribution of help to the needy.
I found it very true that different people learn in different way from my effort on sharing the details of programming and math with fellow co-worker and interns too.
Try make 30 people grab the same details (programming/details) and you will learn a lot about what you teach about and also on how people learn.
When i understand that, i ultimately understand the reason why there is so much debate and on going discussion about some particular details: much of our confusion were caused by lost of context in communication.
[edit: typo]
ps: great tools like kanban should be easy to implement and easier to understand.
Good thinking preceeds technical mastery. Mastery in any skill (which is basically any applied knowledge) can be learnt by apprenticeship for a period of time.
It takes a jedi to train a padawan.
I believe that the "not so good in exam" type is excellent in another thing aside academic, and that thing usually make them leader.
I assume remote working will be unbanned in near future if the condition allowed.
Aggree on we need more creativity and a piece of certificate does not mean a job.
Reason marketing is effing hard (for us programmers) = human is fickle and feedback is sporadic.