|
PIEBALDconsult wrote: which is a benefit of working in an office It works just the same way WFH. But in that instance, if it "hits me" 20 minutes after "leaving" work then I'm in the garden, or putting away the washing and I can just pick up the laptop and at minimum write myself a note about my new brilliant idea, if not implement it fully, decide it's complete rubbish and roll everything back. Rather than be doing 70 (or more likely 15) up the motorway only to be distracted by some idiot who thinks "mirror, signal, manoeuvre" is for wimps and forget all about it. The mind never shuts down; just goes into "energy saving" mode...
|
|
|
|
|
YMMV.
I have always* understood the wisdom of getting away from it (whatever it is) and having a fresh eye on it later.
Yet, my experience (during lockdown) was that I just continued to sit at my desk looking at the code until it fixed itself. When the work is at home, getting away from it can be more difficult, in my experience.
* Since art classes in high school anyway.
|
|
|
|
|
I often get my best ideas in the shower. It got so frequent I had one boss tell me the company should pay my water bill.
"They have a consciousness, they have a life, they have a soul! Damn you! Let the rabbits wear glasses! Save our brothers! Can I get an amen?"
|
|
|
|
|
Well, ummm, during lockdown my personal hygiene was somewhat lacking as well.
|
|
|
|
|
As well? Mine was not lacking at all and I have no idea why you would think it was.
"They have a consciousness, they have a life, they have a soul! Damn you! Let the rabbits wear glasses! Save our brothers! Can I get an amen?"
|
|
|
|
|
I meant -- as well as (perhaps) my coding hygiene.
|
|
|
|
|
So did you take your boss up on the offer?
|
|
|
|
|
No, they laid me off shortly after that. Thankfully, I am finally at a company that doesn't do lay offs. It helps that it is privately held and doesn't have to kiss the backsides of investors.
"They have a consciousness, they have a life, they have a soul! Damn you! Let the rabbits wear glasses! Save our brothers! Can I get an amen?"
|
|
|
|
|
For me, I usually get that "aha" moment at 3:00 AM. Forget about sleep after that.... 😳
|
|
|
|
|
PIEBALDconsult wrote: I've learned not to kid myself that the code I just wrote, tested, and checked in can't be improved after looking at it again some time later.
I have learned that no one writes code that cannot be improved.
Certainly some parts of code that were created by one person certainly seem ideal. But the totality of work by one author will always have places where things could have gone better.
|
|
|
|
|
that's top-down methodology...
diligent hands rule....
|
|
|
|
|
There's a subtle difference between production ready, and functionally complete.
It's (for me) always worth thinking through what the functionally complete (System Engineered) version could include and how it may become over complex with contradictory requirements. Sometimes there are subtle choices that lead to the death-march pit of doom while a slightly different choice would clearly signpost the sunlit uplands of future success.
Then you can focus on the core element, the 'spike', where the tyres hit the road and the concepts hits the existing code, and neater approaches to the same functionality do start to emerge.
Moving fast, always broken, like a bull in a china shop, is not a good look! Production ready is good, full function extendable is even better
|
|
|
|
|
That is the Hardware way, going full Mandoliran. If you have to hardware tasks get one step at a time is best. I must admit once Visual Studio comes out very seems to be an expert and often tells you you are taking too long you don't need 'try ... catch', test it 'you screwed up with lenght that could be entered' out comes try...catch.
|
|
|
|
|
This is the way.
"I have no idea what I did, but I'm taking full credit for it." - ThisOldTony
"Common sense is so rare these days, it should be classified as a super power" - Random T-shirt
AntiTwitter: @DalekDave is now a follower!
|
|
|
|
|
Out of interest, did you watch The Book of Boba Fett as well?
I just finished bingeing it and am looking forward to series 2, if it ever happens.
"I have no idea what I did, but I'm taking full credit for it." - ThisOldTony
"Common sense is so rare these days, it should be classified as a super power" - Random T-shirt
AntiTwitter: @DalekDave is now a follower!
|
|
|
|
|
If I'm coding in an area that is new to me I start out with, what I call learning code or POC code.
Once I learn the system to my satisfaction I straighten out and optimize the code to a working state.
Or abandon it and wonder what the hell I was thinking even messing with it.
PartsBin an Electronics Part Organizer - An updated version available!
JaxCoder.com
|
|
|
|
|
ditto
"A little time, a little trouble, your better day"
Badfinger
|
|
|
|
|
Just and FYI - it's not really a dirty secret or something to be ashamed of (not saying you are, at all ).
its called the Explorative/Ideate phase of Design Thinking. Its a precursor to the prototype phase.
Understand
Explore (Ideate --> Prototype)
Materialize
|
|
|
|
|
Like anything with tech, there's an art, and with that, that means there's no one size fits all approach IMO.
For instance, if I'm creating a POC or just want to toss something together to see if the program can be useful before I put real effort into it, then rolling out a few iterations that aren't perfect, just to see the concept is ok. If it turns out being useful or someone else will ever see the code then it can be re-designed.
Keep in mind though, on a functional/unit level, it's always strive to do things the right way. More so talking about the architecture aspect.
However, if I'm being paid to develop something, then it's not really my job to see if the app is viable or not. It's my job to just make the thing. In that instance I'll put in the effort to think about design as a whole upfront.
So, it really depends.
Jeremy Falcon
|
|
|
|
|
I agree with you.
Yes, yes... you read it right
If it is something private... it is like v0, v00, v00+ until it gets to v1 in a nice form.
If it is for work... I prefer to do like (I don't remember who told it but... anyways): If I have 8 hours to chop a tree, I will spend 6 hours sharpening my axe.
M.D.V.
If something has a solution... Why do we have to worry about?. If it has no solution... For what reason do we have to worry about?
Help me to understand what I'm saying, and I'll explain it better to you
Rating helpful answers is nice, but saying thanks can be even nicer.
|
|
|
|
|
I agree also.
"A little time, a little trouble, your better day"
Badfinger
|
|
|
|
|
Nelek wrote: Yes, yes... you read it right
Nelek wrote: I will spend 6 hours sharpening my axe. It just makes sense. Time and time again I've seen "spaghetti code" projects because folks don't take the time to do that.
Jeremy Falcon
|
|
|
|
|
|
Yep ... I've refactored, and factored back again. Created "new" routines I had already created (and forgot about). It's called: "Flow".
"Before entering on an understanding, I have meditated for a long time, and have foreseen what might happen. It is not genius which reveals to me suddenly, secretly, what I have to say or to do in a circumstance unexpected by other people; it is reflection, it is meditation." - Napoleon I
|
|
|
|
|
Guilty
I keep refactoring till I retire.
I'm a C# developer.
With every new version of the language, I look at my code to see where I can 'fit it in' the new stuff.
I found a module last week that I refactored 98 times in the past 3 years.
My mantra is:
First make it work, the refactor it till it doesn't, and finally start over.
|
|
|
|