Ten minutes later, new question. Same process:
- Gather everybody around.
- Answer the question, and explain the philosophy.
- Make sure everyone understands the thought process.
- Ask one person to write it in the manual.
- Let them know they can decide this without me next time.
After two months of this, there were no more questions.
Sounds simple, but sometimes getting people to think for themselves requires you to repeatedly explain the thought process...
Steve has posted another epic rant on Google+ about the Software Engineerings own political axis. My favorite part it the characterization of the Conservative View as Fred from Scooby-Doo and the Liberal View as Shaggy. The views are highlighted below
- Software should aim to be bug free before it launches.
- Programmers should be protected from errors.
- Programmers have difficulty learning new syntax.
- Production code must be safety-checked by a compiler.
- Data stores must adhere to a well-defined, published schema.
- Public interfaces should be rigorously modeled.
- Production systems should never have dangerous or risky back-doors.
- If there is ANY doubt as to the safety of a component, it cannot be allowed in production
- Fast is better than slow.
- Bugs are not a big deal.
- Programmers are only newbies for a little while.
- Programmers figure stuff out amazingly fast when their jobs depend on it.
- Succinctness is power.
- Rigid schemas limit flexibility and slow down development.
- Public interfaces should above all else be simple, backward-compatible, and future-compatible.
- System flexibility can mean the difference between you getting the customer (or contract) vs. your competitor nabbing it instead.
- Companies should take risks, embrace progress, and fiercely resist ossification
- Premature optimization is the root of all evil.
Excerpted from "Notes from the Mystery Machine Bus" by Steve Yegge
I'm pretty sure the concept of a hidden file was an unintended consequence. It was certainly a mistake.via plus.google.com
How many bugs and wasted CPU cycles and instances of human frustration (not to mention bad design) have resulted from that one small shortcut about 40 years ago?
Keep that in mind next time you want to cut a corner in your code.
As well considered Unix always seemed to be, the notion that hidden files were an unintended consequence of a "quick hack" is amusing...
Slowgrammers are like poison to a team. Just like that old saying “One bad apple can spoil the whole bunch”, One person within a team can bring the team down to their level. The team can sometimes only go as fast as their slowest player.via sparkoverflow.com
As for Borodin, he didn’t seem particularly concerned about what Apple does next. Asked if he was afraid about what Apple’s response to him directly might be. “No,” he replied, adding, “I’m a happy user of iPhone 4S … I think they will hire me.via macworld.com