I left a company when management decided to discontinue a product right after we finally made its code more maintainable.
Had a look at the product that would replace it, and it was a bigger mess from what we started with.
I left a company when management decided to discontinue a product right after we finally made its code more maintainable.
Had a look at the product that would replace it, and it was a bigger mess from what we started with.
If a team member can fuck up the history you probably should look into your merge policies.
It’s probably just some basic script triggering on stuff like “died”, “all lost” and “I have nothing”.
Version numbering scenes are also arbitrary. In the case of Linux, the scheme is “Bump up the minor version until it’s too big. In that case bump up the major version instead”.
The terminal is a power tool. I can do stuff with it that’s slow or inconvenient with graphical tools.
I really like the piping capabilities of the Linux terminal. Incredibly useful for text processing.
I’m also glad I did it as a hobby before I started viewing software development as a job. No code from me if there’s no money on the table.
“Due the global economic circumstances, we were forced to make the incredibly tough decision to say good bye to one of our staff members, cutting down the work force by 100%”
I don’t think Sean makes as many public appearances anymore, so probably safe. But who knows what he will do.
You can’t rescue the princess, but you can borrow her.
He has used this comic as his profile pic on Twitter and StackOverflow for quite a while.
How is that going to help artists getting paid?
Seems like they’ve fixed it now, but there was a time when they had proof of stake without withdrawal functionality
Haven’t checked it in a while, but is it still impossible to withdraw staked coins?
That’s basically it, except everything is darn expensive.
My job title is actually a data scientist. I’ve seen few pieces of code that couldn’t have been made more explainable by just using a more clear and concise naming of variables and functions. Don’t try to be so overly clever with your single letter variables and Greek alphabet. Just explain what it is with a good name.
If I’m lucky I get to write a cool new algorithm once per quarter or so. Usually it’s just a standard algorithm that has an explanation in a Wikipedia page, so I just give the name of the algorithm and a link to that page.
Most of the time we’re just doing basic data processing building on the preexisting solutions. These generally don’t need comments.
The worst code is usually when someone has tried to be overly clever (including myself). Often a simple and straightforward solution had been overlooked. Simple solutions are easier to understand and maintain. Anyone can just look at the code and get a sense of what’s going on without any comments. In many cases a simple solution has also more accurate and faster to compute.
In my work, having explainable results far outweighs anything else, and you don’t get that by writing difficult to understand code.
If you’re working in embedded I guess you can probably make an inline function or a macro so it’s taken care of at compile time.
One example was when a method’s documentation said that it would throw a certain exception. Turns out it was actually throwing a different exception (deep into the code), so no wonder why we never captured it in time.
It’s probably a little bit slower, but there are other things more worth to optimize than to shave off a few microseconds from a 15 minute delay.
I think most people fail to understand what code smell really is. They think code smell means bad code. A code smell is actually an indication that something else might be bad with the code. The code smell itself might not be bad.
So when a code smell appears, it means you should identify the reason it exists and potentially fix it. In this case the bad code is a buggy external library, which is difficult for you to fix. Therefore, leaving the “code smell” is the best course of action.
Your manager was in the wrong and you were right to write comments.
Wait until AI start to summarize meetings into email