|
Professionally:
6502 Assembly
A month later, I taught myself C using 8086 to figure out what C was doing. Two days later, I had the epiphany that C was a great macro assembler.
|
|
|
|
|
Various flavours of BASIC including with BASCOM
Fortran
xBase Clipper
Peter Wasser
"The whole problem with the world is that fools and fanatics are always so certain of themselves, and wiser people so full of doubts." - Bertrand Russell
|
|
|
|
|
|
The Federal Communications Commission has officially begun to undo Obama-era regulations on Internet service providers, often called net neutrality rules. I'd make a D&D joke here, but I'm not sure what the alignment will be changing to
Whichever side of the issue you're on, I stand by our decision that this is news worthy of the newsletter. And this was as neutral a news article as I could find on the topic.
|
|
|
|
|
Like everything else in the current maladminstration, chaotic stupid.
Did you ever see history portrayed as an old man with a wise brow and pulseless heart, waging all things in the balance of reason?
Is not rather the genius of history like an eternal, imploring maiden, full of fire, with a burning heart and flaming soul, humanly warm and humanly beautiful?
--Zachris Topelius
Training a telescope on one’s own belly button will only reveal lint. You like that? You go right on staring at it. I prefer looking at galaxies.
-- Sarah Hoyt
|
|
|
|
|
Quote: what the alignment will be changing to
Lawful Evil, of course! The alignment of most governments.
- I would love to change the world, but they won’t give me the source code.
|
|
|
|
|
The Mac and iOS software developer Panic has had the source code for several of its apps stolen. But did they panic?
|
|
|
|
|
They've discovered that a towel was used in the break-in and the hackers left a message for the company about how they had obtained access.
"So long, and thanks for all the phish."
|
|
|
|
|
Developers can apply for the contest by sending in a proposal consisting of art, video, and full details of the idea. It's not like there's much competition
|
|
|
|
|
So basically, Microsoft an Unity will receive lots of ideas, most of which won't be selected, but have enough information to make them a marketable product. Reminds me of that old 80's song Money For Nothing by Dire Straits.
When you are dead, you won't even know that you are dead. It's a pain only felt by others.
Same thing when you are stupid.
modified 19-Nov-21 21:01pm.
|
|
|
|
|
I believe you hit the nail on the head.
"the debugger doesn't tell me anything because this code compiles just fine" - random QA comment
"Facebook is where you tell lies to your friends. Twitter is where you tell the truth to strangers." - chriselst
"I don't drink any more... then again, I don't drink any less." - Mike Mullikins uncle
|
|
|
|
|
Humans have accidentally created a protective bubble around Earth by using very low frequency (VLF) radio transmissions to contact submarines in the ocean. And soon we shall emerge as beautiful space butterflies
|
|
|
|
|
Mind-controlled prosthetics could be here sooner than we expected. Turn on, jack in, drop out?
|
|
|
|
|
Kent Sharkey wrote: Turn on, jack in,
or Jack-off?
#SupportHeForShe
Government can give you nothing but what it takes from somebody else. A government big enough to give you everything you want is big enough to take everything you've got, including your freedom.-Ezra Taft Benson
You must accept 1 of 2 basic premises: Either we are alone in the universe or we are not alone. Either way, the implications are staggering!-Wernher von Braun
|
|
|
|
|
On the subject of comments, programmers seem to fall roughly into two camps. These include the “clean code needs no comments” camp and the “professionalism means commenting” camp. /* Holy war goes here */
Replace with #, ', ; or whatever your marker of choice.
|
|
|
|
|
Comment everything and let people know what you've changed.
/**** THIS IS FIXED ( ͡° ͜ʖ ͡°) ****/
|
|
|
|
|
Robert C. Martin in Clean Code pg. 53-54 wrote: If our programming languages were expressive enough, or if we had the talent to subtly wield those languages to express our intent, we would not need comments very much—perhaps not at all. The proper use of comments is to compensate for our failure to express ourself in code. Note that I used the word failure. I meant it. Comments are always failures. We must have them because we cannot always figure out how to express ourselves without them, but their use is not a cause for celebration.
The only thing I would add to this is that XMLDoc comments are fine for documentation/release purposes. You can't expect someone to read your whole library so help em out with Intelli-sense.
|
|
|
|
|
I think that article implies comments within code blocks (e.g. inside a function). In which case I fully agree, though the "failure" isn't always just the programmer's fault, sometimes it's the language itself causing such unclear code that a comment is needed to explain what's going on (or more properly WHY).
To me those XML comments are actually documentation, not simply comments. And we all know how we feel about using a library where the documentation is non-existent or lacking detail. The fact that some tools like VS bring these documentations into the intelli-sense arena is just an extra boon. Similarly (and before Intelli-sense / contextual-auto-complete) these sorts of things could just be converted to help files or web pages - for manual lookup (did this pretty often in Java in the 90s).
|
|
|
|
|
I agree. As Martin said, "If our programming languages were expressive enough, or if we had the talent to subtly wield those languages to express our intent, we would not need comments very much—perhaps not at all." Also to your other point, comments and documentation can often overlap but they are nonetheless distinct entities. Comments exist to clarify intent or methodology while documentation exists to clarify usage.
|
|
|
|
|
irneb wrote: I think that article implies comments within code blocks (e.g. inside a function). In which case I fully agree, though the "failure" isn't always just the programmer's fault, sometimes it's the language itself causing such unclear code that a comment is needed to explain what's going on (or more properly WHY).
I agree. Certainly when maintaining code I often encounter the situation that I understand what the code is doing clearly enough but often not why. Though sometimes a why comment could be moved into what you call the documentation comment below, e.g., could be put into the remarks section.
irneb wrote: To me those XML comments are actually documentation, not simply comments. And we all know how we feel about using a library where the documentation is non-existent or lacking detail. The fact that some tools like VS bring these documentations into the intelli-sense arena is just an extra boon.
Yes, as said in one of my other replies, I aim to have only documentation comments, not inline code ones (though sometimes unavoidable).
Kevin
|
|
|
|
|
I agree with that. I strive to achieve a situation in which I only have XML Doc comments (or, in general class/function header comments) and no inline comments. Essentially my maxim is: if it's possible to express it clearly in code then express it.
Kevin
|
|
|
|
|
Comments!?! I haven't made it past the TABS vs SPACES war yet.  
When you are dead, you won't even know that you are dead. It's a pain only felt by others.
Same thing when you are stupid.
modified 19-Nov-21 21:01pm.
|
|
|
|
|
|
When you are dead, you won't even know that you are dead. It's a pain only felt by others.
Same thing when you are stupid.
modified 19-Nov-21 21:01pm.
|
|
|
|
|
You can fight multiple wars at the same time.
Also tabs are superior in every way. Come at me 
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
