|
Eddy Vluggen wrote: I distrust any app in the hospital. If it works, ship it, right?
This isn't a medical application.
Eddy Vluggen wrote: The issue is that my metadata functions and helpers aren't documented as much as they need to be
Because I am human, mortal, and have finite amounts of time and energy.
Check out my IoT graphics library here:
https://honeythecodewitch.com/gfx
And my IoT UI/User Experience library here:
https://honeythecodewitch.com/uix
|
|
|
|
|
honey the codewitch wrote: Because I am human, mortal, and have finite amounts of time and energy.
What kind of excuse is that? 
Seriously, I would mostly prefer to have clear, maintainable code than a tour de force like you wrote, even at the cost of performance. The only exceptions are when the function is the one preventing the program from meeting some performance bar.
Freedom is the freedom to say that two plus two make four. If that is granted, all else follows.
-- 6079 Smith W.
|
|
|
|
|
My code is quite extensively documented, just not all the dark corners that only I end up needing anyway. Pixel metadata is one of those things.
People don't really need to know how many bits exist to the left of an arbitrary pixel channel, and if they really do they can look at the comments in the source code.
Check out my IoT graphics library here:
https://honeythecodewitch.com/gfx
And my IoT UI/User Experience library here:
https://honeythecodewitch.com/uix
|
|
|
|
|
honey the codewitch wrote: Because I am human, mortal, and have finite amounts of time and energy.
You, mortal?
Erlkönig: programmer-and-the-devil.shtml[^]
Bastard Programmer from Hell 
"If you just follow the bacon Eddy, wherever it leads you, then you won't have to think about politics." -- Some Bell.
|
|
|
|
|
It works and has a sole responsibility. If it was to be refactored, you could use chain of responsibility to break it up.
Graeme
"I fear not the man who has practiced ten thousand kicks one time, but I fear the man that has practiced one kick ten thousand times!" - Bruce Lee
|
|
|
|
|
It would require duplicating a lot of code because most of it is compile time computations of the sort that aren't easily passed to another function, even at compile time. That's the other issue with breaking it up. There would need to be a large common preamble to each routine.
Check out my IoT graphics library here:
https://honeythecodewitch.com/gfx
|
|
|
|
|
Ah, so for IOT, where memory is a premium, it's better not to. Totally understand. 😊
Graeme
"I fear not the man who has practiced ten thousand kicks one time, but I fear the man that has practiced one kick ten thousand times!" - Bruce Lee
|
|
|
|
|
A certain U.S. courier company doesn't allow capital letters in the @ part of an E-mail address. 
|
|
|
|
|
Write it low case...   
sorry... too tempting
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.
|
|
|
|
|
|
Perhaps their software vendor charges them for each letter that requires a lower case conversion? 
|
|
|
|
|
Capital letters are larger than lower case letters so they take up more disk space.
For such a large company with so many customers, that space is adding up!
This started out as a joke, but the thought occurred to me that something like that may actually have been the rationale behind it 
|
|
|
|
|
Sander Rossel wrote: Capital letters are larger than lower case letters so they take up more disk space.
No. Uppercase A-Z has values from 65 to 90, while lowercase a-z has values from 97 to 122.
This refers to ASCII. Uppercase can be encoded in as little as 5 bits (Baudot code) or 6 bits (Univac Fieldata; there are other 6 bit encodings as well).
If space is really at premium, you should go for Morse code. Lots of people never realized that the coding table is sorted by frequency: E, the most common letter (in English), is a single 'di'. T, the second most common letter, is a single 'dah'. The third most common is I, so it is 'di di', #4 is A: 'di dah', #5 is N: 'dah di', #6 is M: 'dah dah', all the way to rarely used special characters, such as colon: 'dah dah dah di di di' or comma: 'dah dah di di dah dah'.
We may argue the frequencies, and for other languages than English they may be significantly off. For special characters, usage may have changed since 1844. Nevertheless, the fundamental principle behind the Morse code is frequency sorting, to reduce the time for transmitting a message to a minimum.
|
|
|
|
|
I think Sander forgot the joke icon. 
|
|
|
|
|
Because I actually mentioned "This started out as a joke, but..." 
|
|
|
|
|
So when you got to the end it was no longer a joke ... 
|
|
|
|
|
I didn't include it myself. Having to explain, or point out explicitly, humor / parody / irony takes the sting/humor out of it.
Also: I didn't succeed in finding any good translation of the 'gruk' (mini-poem) by the Danish author Piet Hein, but my un-poetic translation says
He who takes a joke as nothing but a joke
and sincerity as nothing but sincerely
he actually understands both kinds
rather poorly.
(If anyone knows a better translation, please let me know!)
|
|
|
|
|
Well, you put us all to shame. A dutch speaker translating a Danish poem into (quite good) English.
|
|
|
|
|
He who only takes a joke as a joke
and sincerity as sincerity
needs to be knocked on the head.
|
|
|
|
|
Sander Rossel wrote: This started out as a joke, but
If you read my message you could've saved your whole reply.
Now that's a lot of bits! 
|
|
|
|
|
I get it: You don't want anyone to extend on your joke, you want to have the last hand on it.
That's OK with me ... But you'll have to formulate a response to this post as well of you insist on having the last word
|
|
|
|
|
Seriously?
sorry, too tempting
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 like when they don't allow dots.
Check out my IoT graphics library here:
https://honeythecodewitch/gfx
|
|
|
|
|
so you have to spell them out 
|
|
|
|
|
Actually, that's not a bad thing. Yes, we treat it as case-insensitive, but the original concept had lowercase letters in mind. These days, uppercase is used as a crutch because you have a really long username or domain name, or just are an old fart. 
bob@bob.com - Good
bobGoesToTheMarket@bob.com - Bad
P.S. They probably should just lowercase it on the backend and allow for mixed cased input though.
Jeremy Falcon
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
