not HD mode. stable chrome for mac 10.6.
1,461 karma · joined October 15, 2008
not HD mode. stable chrome for mac 10.6.
I have first hand experience with this and I think it is not only possible, but a reasonable goal for any well designed product. (the advantage of dynamic feature walls is already a huge win)
(wrt free time, i would say: stop procrastinating! i'm lucky, because i naturally prefer to work immediately and then be able to spend my free time exactly as i prefer, rather than wasting time and working under pressure near deadlines. if you can figure out how to trade your procrastination time for real pleasure, then you win both now and later.)
Chris seems to be really decent. even if he had a lapse in judgement, he embraces pleasant discussion. i'm embarrassed by the juvenille response: the meanness most of all, but also the unwillingness to see someone else's perspective or view efforts as a collaboration rather than a fight.
if a teammate messes up, you help them, you don't shoot them down.
i haven't yet figured out the right words, but there's something important i'm trying to communicate. feedback welcome.
Good design is hard.
this makes for a double whammy in terms of extensibility, since not only is the code literally more conducive to later changes, but it meets developer's expectations, too.
encapsulation and inheritance go hand-in-hand in my book, though i suppose encapsulation, and the necessary concept of interface contracts, is an axiom of sorts from which many other good practices can result, especially if there is also a culture of "communicating for extensibility by new developers later."
if programming was a single skill, being on team wouldn't be so awesome (and working with other programmers is definitely awesome).
I put pictures of adventures and creations on facebook as viewable by anyone with a facebook account. People who vaguely run into me can go there and find out more of who I am...sort of like a resume for friendship (tactless). We also find common interests, conversation starters, etc. I naturally make friends in person; to me facebook is just one more neat tool in the toolbox for forging and maintaining social connections and fun in general.
however, i think there is a continuum of methods, from TDD to proving correctness. it is often practical in the real world to do up front design before hacking out some code. i believe super smart hackers actually make lots of smart design decisions when "hacking" out code, whether that is realizing the appropriate loop invariants to make an algorithm work or figuring out the right abstractions for reusable code. there's lots of ways that good forsight produces correct code faster. that's what intelligence is: thinking, not brute force.
the smart coder, especially after gaining a variety of experiences and learning from different mentors, takes pieces of different methods in order to simultaneously make headway on different goals, not just correctness and extensibility, but refactorability, fast-rampup for new team members, fun, etc.
i have a dog and i live with 8 other people, so i have a bit of data on 8 different dog-human relationships. it boils dog to the dog treating everyone differently depending on who gives him food. P always give dog his sandwich crusts without asking anything in return, so when P walks in the door with a subway, dog goes grazy. in fact, P started giving more when dog wimpered, so for a little while dog whimpered until i made P not be such a sucker. A always lets dog lick his plates, so dog gets excited when A finishes eating. L requires dog to lie down in a neighboring room, so dog beg's from neighboring room when L eats. it's not love or care, it's simple causation and reward. dog constantly tries different tactics on those people who give him food. often, the amount of food escalates.
btw, dog goes crazy when the (human) dinner bell is rung.
edit: also, in restaurants, bribing before is a bit like tipping afterwards. the wait staff is constantly evaluating how much effort to expand on incoming parties (among other things) in order to maximize tips. in light of that, treatin an apparently wealthy couple well in hopes of a good tip isn't unreasonable. as for accepting bribes...depending on the place it's not that different from a tip except that it comes before not after the service (some places split tips with the whole staff, including say back waiters, etc, so then it might be immoral if the people keep the bribe for themselves. as for the immorallity of "jumping" the queue--for all i know, the wait staff does that anyway when they evaluate how much people can tip....)