|
Wordle 457 6/6
⬛⬛⬛⬛🟩
⬛🟩🟩⬛🟩
🟩🟩🟩⬛🟩
🟩🟩🟩⬛🟩
🟩🟩🟩⬛🟩
🟩🟩🟩🟩🟩
Get me coffee and no one gets hurt!
|
|
|
|
|
Wordle 457 5/6*
⬜🟩⬜⬜🟩
⬜🟩🟩⬜🟩
🟩🟩🟩⬜🟩
🟩🟩🟩⬜🟩
🟩🟩🟩🟩🟩
This was beginning to look familiar.
|
|
|
|
|
Wordle 457 5/6
⬜⬜🟩⬜⬜
🟩🟩🟩⬜🟩
🟩🟩🟩⬜🟩
🟩🟩🟩⬜🟩
🟩🟩🟩🟩🟩
Got off to fast start then too many options.
"A little time, a little trouble, your better day"
Badfinger
|
|
|
|
|
I wonder how many of us do it? I do.
I frequently mentally compare code I see with what I would have written myself, and I do so not to critique other people's code (though it happens) so much as to understand myself and the way I write. Introspection after all, isn't automatic, be it with code or otherwise.
I've noticed some pretty interesting things in the process. I don't know how much the activity has actually influenced my coding style. The biggest change to the way I code that has ever happened to me happened in 2018. I don't solve problems by breaking them into their component pieces anymore. I attack problems more ... holistically? now. It generally makes for efficient, but less intelligible code. The way I think changed. Some ways for the better, other ways not, but it impacted how I write software, among other things.
Cons: Compared to much of the code I see in the wild, my functions are long, my solutions aren't as readable, some things are so instinctual to me I forget to comment.
Pros: My code generally works, and does so well when it does. In some ways, cutting down on the abstractions leads to simpler code, or at least the surface area/API of said code is simpler, if I'm making a library for example.
I see the above as a net win, but only marginally so, and maybe most of that small net advantage can be chalked up to natural, incremental evolution rather than my 2018 watershed event.
I enjoy thinking about this stuff, but I'm not sure if it's beneficial, or me just passing time.
Your thoughts?
To err is human. Fortune favors the monsters.
|
|
|
|
|
It sounds like we start similarly but have different outcomes. Most of the code in my repository--some 235 KLOCs--had little up-front design. I just have something in mind and start coding. But with empty functions to be filled in later, merciless refactoring, and creating new functions whenever code fragments are duplicated. This usually results in small functions, though I don't mind a long function if breaking it up would add no value other than satisfying some arbitrary maximum length.
The downside is that I could sometimes save time by doing more up-front design. The upside is that time spent on more than a cursory up-front design is usually wasted. The code has to be written so that it can speak to me.
|
|
|
|
|
I've always been blessed by being able to quickly produce and visualize even complex designs without writing them down, which I primarily do for the benefit of others.
And I can do it in tandem with coding. It's a gift. I was a software architect for a time, so I understand design principles, and the rules of engagement. I just break them because I can get away with it and still produce solid designs.
https://honeythecodewitch.com/gfx
I've been adding to this for over a year without fundamentally changing the architecture. I started with gfx_pixel.hpp and went from there, building up bitmaps, and then drawing functions, and then on to more complicated things. And I future proofed it for the most part. It hasn't had a major refactor because aside from some necessarily grotty internals I'm not sure *how* to refactor, it doesn't need one.
But I am abysmally bad at defensive coding, or coding to a precise specification, like you find with bare metal embedded sometimes, or medical or bank software.
To err is human. Fortune favors the monsters.
|
|
|
|
|
Heh, bare metal embedded design/coding is exactly what I've been doing for most of my career (retired now). It's what I enjoyed the most. And yes, after a number of years in the business, the overall design of a project just seemed obvious after reading a spec.
|
|
|
|
|
Mostly ditto.
I do a little more up front designing but it's mostly a research of previously written applications. I do try hard to be consistent with naming, etc. for my future benefit and the benefit of those who might have to maintain it. BTW it's all various generations of ANSI C.
Honey's approach is a gift many of us do not have.
"A little time, a little trouble, your better day"
Badfinger
|
|
|
|
|
You don't write code for yourself, or even for the compiler; you write it for the poor soul who has to maintain your code when you have moved on. Therefore:
- The code should, as far as possible be self-explanatory - meaningful variable /function / ... names, etc.
- Where the code is not self-explanatory, it must be commented sufficiently to explain what you have done.
- Ideally, all functional blocks should appear once, and once only, in the module. This implies refactoring common code into functions, etc.
- A design document is typically necessary in order to explain your decisions. This cannot be replaced by comments in the code!
Anything and everything else (code formatting etc.) is a matter of personal taste. Many companies have guidelines that might clash with your preferred style, but this is not a hill to die upon.
Freedom is the freedom to say that two plus two make four. If that is granted, all else follows.
-- 6079 Smith W.
|
|
|
|
|
An upvote despite (a) after I've moved on, I no longer care; (b) formatting guidelines that clash with my style are simply wrong. 
|
|
|
|
|
You italicized “wrong”. It should be in bold!
If you can't laugh at yourself - ask me and I will do it for you.
|
|
|
|
|
Greg Utas wrote: after I've moved on, I no longer care
IMO, as professionals, we have a duty of care to ensure that software we write for hire is maintainable. Software we write for ourselves can be as messy as we like. 
Greg Utas wrote: formatting guidelines that clash with my style are simply wrong
I didn't say that they aren't wrong; I said that it's not a hill to die upon.
Freedom is the freedom to say that two plus two make four. If that is granted, all else follows.
-- 6079 Smith W.
|
|
|
|
|
I didn't write this post about what I'm supposed to do. After 30+ years of development, most of that time professionally, I know how I'm supposed to write code.
I wrote this to talk about how I *do* write code, warts and all.
To err is human. Fortune favors the monsters.
|
|
|
|
|
honey the codewitch wrote: After 30+ years of development, most of that time professionally, I know how I'm supposed to write code.
After 30+ years of code development, what you should do should be the same as what you do! Not following accepted practice may be acceptable in an inexperienced developer (that's why we have code reviews - to help them learn), but is inexcusable in one as experienced as you.
Freedom is the freedom to say that two plus two make four. If that is granted, all else follows.
-- 6079 Smith W.
|
|
|
|
|
There's a difference between less readable and not readable, and I code on IoT. I don't have the RAM or CPU for your abstractions.
To err is human. Fortune favors the monsters.
|
|
|
|
|
You say that you write "less readable" long functions. Breaking that down into smaller, meticulously named functions, would hardly lead to a significantly heavier footprint, methinx. If nobody else ever needs to dive into your code then
either is fine. But... As others already say: If other folks need to modify your code then it is reasonable to make it easier for them.
And, if one day - by some weird unearthly accident - you would happen to end up in a project with much more people and RAM, would you then write "more readable" code?
"If we don't change direction, we'll end up where we're going"
|
|
|
|
|
I can't remember something if it's offscreen for even a few minutes - my short term memory is shot. That's why my functions are longer. On the other hand, functions that have high "cognitive load" attached to them don't bother me. So for me, longer functions makes it possible for me to navigate my own code.
When I wrote business software, I usually stuck to patterns so closely that my code could pretty much be generated. Then I often generated it.
Nowadays there are entity frameworks and ORM things out the wazoo so I don't even know what people are writing these days, other than sticking business rules into a repository like an RDBMS or something.
I'm happily so far removed from that stuff these days it's a different world.
And I really have no desire to develop desktop or even phone apps.
To err is human. Fortune favors the monsters.
|
|
|
|
|
I am no longer a desktop kid either. But I work on servers. Beeeg video servers.
I like to say: "I write code [so readable] that if I get hit by a bus, the bus driver can continue my work."
"If we don't change direction, we'll end up where we're going"
|
|
|
|
|
A wise man once said “Programs are for people to read and only incidentally for computers to execute”.
Mircea
|
|
|
|
|
It's interesting than neither you nor Daniel mentioned anything about code being for the user. 
|
|
|
|
|
Looks like I feel somtehing in the same way.
One does discuss about patterns, refactroring, writing clean code...
... but nobody takes into acount that we should program good programms for the user.
Meanwhile it looks more, that programmers are busy to write code that satisfy themeselve. 
|
|
|
|
|
Users don’t care about the code, only the compiled result.
…and your ability to react to their new enhancement requests.
It is primarily for the second reason that developers worry about code structure.
If it is a write once/run once type program, then neither party cares about the structure very much.
|
|
|
|
|
With the possible exception of libraries targeted at other developers, the code is not for the user; the finished application is.
UX design is an esoteric art in itself, that has its own experts. It is possible to write a program that meets every detail of the technical specification, follows the best design practices, etc., but is unusable.
Freedom is the freedom to say that two plus two make four. If that is granted, all else follows.
-- 6079 Smith W.
|
|
|
|
|
He was one of my instructors at MIT. Very wise in the ways of coding and software engineering in general. It's far too easy to create write-only code and at the time he made his statement about programs being for people to read many languages simply didn't support readable coding as a default. At the time I was at MIT, Ableson and Gerald Sussman taught the introductory software class (6.001) and on the very first day the first thing they did was:
If you've ever programmed before, raise your hand (I remember looking around and there were close to 700 hands raised, including mine).
If you've programmed in any language other than BASIC, lower your hand (I lowered mine as I had Assembler, APL, and FORTH experience.)
For those of you with your hands still up (close to half the class), you will need to unlearn everything you thought you knew about programming.
|
|
|
|
|
Very nice story! Thanks for sharing.
Mircea
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
