|
Knoll’s Law:
Everything you read in the newspapers is absolutely true, except for the rare story of which you happen to have firsthand knowledge.
If you can't laugh at yourself - ask me and I will do it for you.
|
|
|
|
|
|
And if that doesn't fix it, switch to hourly status reports. 
"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!
|
|
|
|
|
OriginalGriff wrote: And if that doesn't fix it, switch to hourly status reports.
Genius!!!
And here I thought you were just an Engineer, but I find out that you obviously have your MBA. 
|
|
|
|
|
I've served my time as Software Manager, Technical Manager, and also Managing Director - and I picked up my management skills from fully trained managers*.
* I watched what they did, and didn't do it.
"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!
|
|
|
|
|
This is typical for me, and part of the reason I produce so many articles for this site.
I don't sleep much these days, but I suppose there is plenty of time for that when I am dead. 
For my last late night stunt, I pulled together a pretty complicated Arduino project and realized that not only did I have libraries that exactly fit what I needed to do, it was all my code - the entire dependency tree except for arduino itself - buttons, encoders, fans, the graphics, etc. All my code.
And I thought "holy heck that's a lot of code. WTF happens to all this when I die?"
For some reason lately I've been a bit morbid regarding code maintenance and project traction.
My graphics library gets plenty of attention these days. It's nowhere near as popular as the big three, but it's a player in the IoT realm, and probably the best one for e-paper, especially color e-paper.
But again, what happens when I die? I actually haven't had to maintain that library for some time, although recently a minor bug was brought to my attention. The drivers have required work though, but they aren't part of the library itself.
People could theoretically take it, keep using it, and work with it, but given how it's built, I'm the only one that can maintain some of that code, and I recognize that. The issue is template metaprogramming which I use in the library to enable some fantastic abstractions for the end user of my code but at the expense of intelligibility of my own code. People that are familiar with C++ metaprogramming are well cognizant of this issue. It's not mine alone.
Still, even among the stuff that people will be able to use in my absence there's plenty to work with.
When the time comes, I'll leave behind a lot of late night endeavors, some curiosities, and hopefully some insight into the craft for others who come after me.
Most of it created at 4am.
Also, egg salad is still chicken salad when you think about it.
To err is human. Fortune favors the monsters.
|
|
|
|
|
For that very reason we all sing "God save the Queen"
"In testa che avete, Signor di Ceprano?"
-- Rigoletto
|
|
|
|
|
Well, by the time you die, your skills and personality will have been encoded into ChatGPT. 
|
|
|
|
|
Once I'm dead, any problems in my code are Someone Else's Problem.
Unless you (a) have dependents, and (b) expect serious amounts of money from licensees, I would simply release the code under an OSS license "as is" or some such. There is no reason why others should not be able to use and benefit from it after I no longer can.
Whatever you decide to do, run it past a lawyer who knows something about IP.
Freedom is the freedom to say that two plus two make four. If that is granted, all else follows.
-- 6079 Smith W.
|
|
|
|
|
Reminds me of all the code escrow BS we used to do with partners at a previous company.
One reason open source is so popular.
|
|
|
|
|
I read the title in the home page "Latest posts" and I instantly knew it was you
GCS/GE d--(d) s-/+ a C+++ U+++ P-- L+@ E-- W+++ N+ o+ K- w+++ O? M-- V? PS+ PE Y+ PGP t+ 5? X R+++ tv-- b+(+++) DI+++ D++ G e++ h--- r+++ y+++* Weapons extension: ma- k++ F+2 X
|
|
|
|
|
Chicken salad and/or Egg salad - love them both
I guess the difference is the age of the chicken.
"A little time, a little trouble, your better day"
Badfinger
|
|
|
|
|
Just add another level of meta-programming. That will fix it!
Have a meta device that is constructed/composed out of any number of smaller meta-devices connected via meta-buses.
Every new project is solved with one definition.
|
|
|
|
|
And put it all in the metaverse. 
Figment of Imagination - Zero Mostel
Freedom is the freedom to say that two plus two make four. If that is granted, all else follows.
-- 6079 Smith W.
|
|
|
|
|
I realize I'm late (very late) to this message/thread--I had it bookmarked 'cuz I wanted to make a point of commenting on it.
It comes to a point where the best you can do is to document things. Not code comments, but describe exactly what version of which build tools you're using (compiler, etc), dependencies (though I realize in this case you're pretty much writing everything yourself), the settings for those tools, and if possible the binaries themselves (the installer) - not just a download link to a third-party site as those can get broken, newer versions can replace older ones, etc.
At work, I've been maintaining (in a shared OneNote book) a page that describes some of the projects I'm working on, and essentially what is a bullet-point list of the tools needed to build them. The idea is, if a newcomer comes in with a brand new machine with just Windows installed, if he follows the bullet-point list, at the end of that, he should be able to build EXEs/DLLs that match exactly what my own system would have produced. Maybe not down to the same hash (build dates do get embedded), but pretty damned close.
I code exclusively on VMs, and every time a new version of VS comes out, I dedicate a new VM for it - I never upgrade, or run multiple VS versions side-by-side. So whenever I start out fresh with a new VM, is an opportunity to revisit those notes and follow them. If something needs tweaking, a library got upgraded to a newer version, etc - I make a note of it to ensure the list as a whole is still valid.
That has saved some new co-workers a lot of grief, and personally I wished every project I had ever worked on had some matching notes to go with it.
Beyond that...understanding the source and making changes to it is another matter entirely. But if a newcomer can rebuild from the source - it's a good starting point.
|
|
|
|
|
I realised I haven't congratulated this years MVPs, and searching through the last few pages, I couldn't find a message to add my congratulations to. So, for those who were awarded MVP this year, congratulations.
[Edit]
Nevermind - I see the MVPs haven't been awarded. As you were, and a pre-emptive congratulations from me.
modified 11-Jan-23 6:28am.
|
|
|
|
|
I'm realising you are a bit early to the party...
"In testa che avete, Signor di Ceprano?"
-- Rigoletto
|
|
|
|
|
|
I see no 2023 MVP list, here at CP.
"In testa che avete, Signor di Ceprano?"
-- Rigoletto
|
|
|
|
|
I just saw that - I edited my message. I should have checked beforehand.
|
|
|
|
|
You are so far ahead! 
"In testa che avete, Signor di Ceprano?"
-- Rigoletto
|
|
|
|
|
It's the recession / inflation - MVP's are cancelled until we all stop striking for more rep points.
"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!
|
|
|
|
|
Given my inactivity here over the last year, I'm ahead of the curve.
|
|
|
|
|
Most Valued Pants? That would be my pajamas 
|
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
