4 ms·
Yeah, that's exactly what I'm doing. Or not. We're way past the decades where you had to sit around "thinking" for ages to come up with a data structure. You s
by mattmanser 12y ago
Yeah, that's exactly what I'm doing. Or not.
We're way past the decades where you had to sit around "thinking" for ages to come up with a data structure. You still loading the program up on cards or something? You saying it is as preposterous as the guy I met a couple of years back who offered to come and design SQL DBs for me. It's just not done any more. That's not how we work any more, that time has past.
In today's world you can prototype up the basics of any complex system in an hour or two and throw it away if it doesn't work. Tests are cheap, it's easy to mock, there's no compilation to worry about. And if you can't look at a problem and immediately see the effective ways you've solved similar problems before, well, you're not as senior dev/architect as you think you are.
You simply sound dated to me.
- bsaul 12y agoIt is indeed a very dated method, but you should try it once. You'll see that by thinking first, coding later, you'll gain a lot of time overall ( you're not always able to see with your code that something doesn't work). Now of course you don't need this method for trivial things, but i hope that's not what you spend most of your time working on. Note: i didn't downvote you.