The Lounge is rated Safe For Work. If you're about to post something inappropriate for a shared office environment, then don't post it. No ads, no abuse, and no programming questions. Trolling, (political, climate, religious or whatever) will result in your account being removed.
I moved back to CA (bay area) when I was 15 with my mom after my father's death. When I was 18 or so, I was over at a a friend's house (cute girl) and her mom handed me an avocado and asked me to cut open "if it was ripe." I had no idea what an avocado would be like when it was "ripe." So I started sawing through it. Never even noticed when I was sawing through the pit. I guess it wasn't ripe.
I am of 3 mind about that....
1. it's so goooooood....
2. but avocado is such a hog on resources, need so much water, destroy community....
3. also good guacamole will need lime/lemon juice.. which I am allergic too
I am a very experienced developer, but I find that my 'process' when I start on some new bit of functionality or sub-system is pretty much bounce off the walls for a while, trying this, discarding it, trying that, discarding it, keep a bit of that attempt, keep a bit of that one, etc... Since I work alone there's no point in writing specifications. All it would result in is that I took a lot of time writing down in detail the first bounce off the first wall, which was then discarded on the way towards the next wall.
Some might say it is time wasting, but ultimately I think it's a wash. The time I would have spent looking 'professional' and writing a bunch of stuff down just gets traded off for trying various things until I find what I like. Given that I almost never do the same thing twice, all the stuff I might write down would mostly be guesses that are probably about as likely to be wrong as right once I really dig into the practical realities of it. And, in the end, I can know for sure that various things that I might have initially discarded really should be discarded, as opposed to actually being a better idea than the one I wrote down so carefully.
Am I the only one who uses the 'Chaos Pattern' as a development tool?
Nope, I'm using Chaos Dev right now. I've re-written all of the compoents for a web project template at least twixe, and a handful of those at least three times. I've tried creating EF data models more than a dozen times.
Since this is going to be used as a basis for all of our apps, it has to be as close to correct as possible before it gets deployed to the rest of the team.
Hell, I'm on the 5th iteration of the template.
Chaos is very much in Chontrol.
".45 ACP - because shooting twice is just silly" - JSOP, 2010 ----- You can never have too much ammo - unless you're swimming, or on fire. - JSOP, 2010 ----- When you pry the gun from my cold dead hands, be careful - the barrel will be very hot. - JSOP, 2013
Last Visit: 31-Dec-99 18:00 Last Update: 21-Apr-21 13:43