Join devRant
Do all the things like
++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatar
Sign Up
Pipeless API

From the creators of devRant, Pipeless lets you power real-time personalized recommendations and activity feeds using a simple API
Learn More
Search - "comment"
-
If you are reading this, I want you to know that I am probably on some kind of FBI watchlist because I googled "How to kill all children while leaving the parent alive". So yeah, Linux is brutal.7
-
My employer has a dev studio in Cali.
The office is gigantic.
It has amenities.
It has a stocked fridge full of iced coffee, energy drinks, and apparently wine.
All the devs have totally enviable hardware.
And they probably earn twice what I do, or at least 50% more.
Yet they write absolute shit, never test their code, and push broken updates every day, often marked as "ready for final testing." Their codebase is full of hacks and guesses and stale cruft and worst practices. I wrote a rant recently about one of their fuckups, which involved 18 million Facebook errors per. day. So that should give you some idea as to the quality of their code, and their level of can't-be-bothered.
Again, they make 50%-100% more than I do.
Their whiny lead dev is bloody lazy when it comes to building things correctly, and totally prefers to half-ass everything and complain instead. He probably makes 150% of what I do, doing like 25% as much work, and maybe 10% as well. Doesn't quite compare though, as he's a Unity dev, not a backend dev. So his work isn't as critical.
akagdkdafavskakeuxbfh.
Bloody pisses me off.
"But their cost of living is higher!"
THEY SHOULDN'T EVEN BE EMPLOYED.rant root gets angry this is the short-short version overpaid crap-tier devs but i got too angry this was originally to be a comment23 -
Only God and I knew what I was doing, writing uncommented code in C a year ago.
Now, only God knows.2 -
After opening the legacy code and finding out that the entire shit has 15000+ LOC and without proper commentsundefined devrant please help fbi fucking comment the code properly comments thensa legacy code notnsa devil wk58 god3
-
I found a really neat way to toggle two implementations using C style multiline comments.
https://twitter.com/_Gaeel_/status/...3 -
INTRODUCING:
---
SYNTAX HIGHLIGHT BOT
---
I have lots of ideas.
This was one of them.
Last week I was playing around with https://carbon.now.sh and found it quite cool!
Then I thought: https://carbon.now.sh supports Twitter. Cool. But what about devRant?
So yeah, then I got the idea: A devRant Bot that generates https://carbon.now.sh images!
Now, 4 days and 800 lines of code later, the bot is ready!
I even had to rewrite the notification checking code 4 times, because none of them worked perfectly...
But on the other hand, the final solution is so good that I want to keep it a secret for now ;D
---
HOW TO USE:
All you need to do is to mention the bot!
Example:
<rant>
@highlight
console.log('Hello World!');
</rant>
The bot then generates your syntax highlighted code (as an image) and posts it as comment a few seconds later.
Everything before the "@highlight" will be ignored!
Example:
<rant>
Look at this code:
@highlight
function add(a) {
return a + 1;
}
</rant>
Here, "Look at this code:" will not be included in the syntax highlighted code.
If the comment text ends right after the "@highlight", the bot wont reply, btw.
---
THEME SELECTION:
That's not all!
You can even select the theme for your syntax highlighted code!
Just go to my other rant and read the instructions!
The theme will be used for every image the bot generates for you!
Link:
https://devrant.com/rants/2178551
---
Feel free to ask any questions in the comments!
My creator (and father thanks to @rutee07), @Skayo, will try to answer all of them!
P.S.: Speaking of @rutee07: I'm a girl. (Also thanks to him)174 -
So my brother had a school project for which he got an 9. I looked at this code and saw this comment. I laughed so hard. 😂24
-
This is what I have to deal with right now... 🙂🔫
Why?
Why would you not comment or name your variables so someone else can understand wtf is going on here?
Why!?16 -
*Typing a message in a modal.*
*Typing a message in a modal.*
*Typing a message in a modal.*
*Typing a message in a modal.*
*Trying to hit Submit button but misses.*
*Accidentally clicks outside.*
*Entire message is gone.*3 -
I really need to get my lazy ass up and get the fuck to work on the privacy site.
Yeah let's fucking do that. I've got a nice special beer as motivation as well!18 -
When you see a comment like this in your codebase:
// I don't know what it does, but touching it will break it!4 -
Stop bitching about having to write comments, they are important whether you like it or not. Trust me nobodys code is "that good" 😒4
-
Happy 0x7E2!
Fun fact:
2018 = 2 x 1009 (both prime)
8102 = 2 x 4051 (both prime)
Let we all finiah at least one side project this year!11 -
How I feel working with code that's been worked on by at least three different teams at three different companies over the past couple of years and not a single person has left any comments or documentation.6
-
Whenever you decide that "This piece code is readable enough" and write a stupidly short comment on it... and you have to revise it 8 months later...6
-
A badass pull request review comment: 'A wise man can learn more from a foolish question than a fool can learn from a wise answer.'2
-
Found this on a client's js code
// They forced me to write this code.
// Prepare yourself.
I found out later that month what that dev truly means2 -
I don't want to come off as a linux-elitist but it's simply amazing how much easier my job is on linux. A good example recently was setting up some libraries for a C++ program I was writing to show to my class. Most of them were using Windows and visual studio, took about 15 minutes to download all the headers and libs, and show them how to configure a VS solution to link them. Not too big a deal but on linux, it only took about 30 seconds to pacman and gcc -l the lib. Little things like that keep me interested in linux as a dev tool.undefined plz dont hate linux no comment on mac ive never worked on one windows is kind of ok too tags are useful tags14
-
Getting ready for production.
Search: console.log
Replace: //console.log
Search: ////console.log
Replace: //console.log
...
Aaaaaand we're good.8 -
When starting a project at work:
My name everywhere. Every file, every change-list I proudly put my name to prove my skills.
Program goes for validation:
Thousands of bugs.
Realize that I've written shit code. Slowly removing my names from all over the code. -
*Me seeing a good rant on devRant.
Wow I have a good thoughts I should comment on it..
*Open Rant, 76 comments (started to be related to the content then won't anymore, jokes and internal jokes)
Oh shit, it'll be useless.. *continue scrolling4 -
Starting a new project:
"I'm gonna write clean and commented CSS today"
===== 20 minutes in =====
"dafuq does this class do? "😣 -
Code comment rant of the day... fcking excel just cost me over half an hour to fix the fking formatting...1
-
Did anybody else know that putting comments in your HTML creates an EMPTY TEXT NODE IN THE DOM?
REAL helpful information when you have to GATHER EVERY ELEMENT WITH TEXT INSIDE OF IT!
WHY WOULD HTML EVEN BE LIKE THIS? IT'S A COMMENT! WHY DOES IT HAVE ANY EFFECT, even if it's minimal, ON THE DOM WHATSOEVER, THIS DOESN'T MAKE SENSE!4 -
In order for the program to run smoothly, it is often necessary to add some comments to the code comments...
/***
* ░░░░░░░░░░░░░░░░░░░░░░▄░░
* ░░░░░░░░░▐█░░░░░░░░░▄▀▒▌░
* ░░░░░░░░▐▀▒█░░░░░░▄▀▒▒▒▐
* ░░░░░░░▐▄▀▒▒▀▀▀▄▄▀▒▒▒▒▒▐
* ░░░░░▄▄▀▒░▒▒▒▒▒▒▒█▒▒▄█▒▐
* ░░░▄▀▒▒▒░░░▒▒▒░░▒▒▀██▀▒▌
* ░░▐▒▒▒▄▄▒▒▒▒░░░▒▒▒▒▒▀▄▒▒
* ░░▌░░▌█▀▒▒▒▒▒▄▀█▄▒▒▒▒█▒▐
* ░▐░░░▒▒▒▒▒▒▒▒▌██▀▒▒░▒▒▀▄
* ░▌░▒▄██▄▒▒▒▒▒▒▒▒▒░░░▒▒▒▒
* ▀▒▀▐▄█▄█▌▄░▀▒▒░░░░░░▒▒▒
*/11 -
Just found this comment in some code I wrote a few months ago... don't think I've ever been more honest!5
-
I like function // (comment) since its the best friend when code is totally fucked up because of bug and best of it its in all languages.
-
Once during a standup, I mentioned that I needed to fix some unit tests before the build would be ready. Our tester then said "no time for tests, we need the build now". That was a dark day.
-
Having trouble logging into an app I am suppose to be working on with another dev. Debugging and found this:
// TODO: Temporary Optional because the API is not working properly
... i'm not happy for so many reasons -
I regret commenting on a WordPress blog using my full name. Although there was nothing stupid on what I wrote, I just hate it that I googled my name and it showed. I just want to delete my useless information / myself on the internet.
Never will this happen again.10 -
Found my old code.
You gotta admit, that's some clean code there, considering I learned C# only for a year at that time.
But those comments....
VeRy WeLl WrItTeN, vErY dEtAiLeD, vErY gOoD9 -
University, Italy
We have sent our code to the professor for correction.
Professor : Who wrote the code with comments in english?
Proud student : me !
Professor : you failed to write the algorithms, and also made mistakes with a lot of English words.3 -
Feature_Request
I suggest, if the OP comments in his/her post, the OP's username should have a red stroke (or whatever color)4 -
Sometimes when I read a rant I upvote one of it's comments. But then I feel like it's unfair for the ranter that a commenter has a ++ and he hasn't, so I upvote the rant too.1
-
/*Why this website does not use slashes to the front of all the comments on a rant is beyond me!*/4
-
Here is another rather big example of how C++ is WAY slower than assembler (picture)
Sure - std::copy is convenient
but asm is just way faster.
This code should be compatible with EVERY x86_64 CPU.
I even do duffs device without having the loop:
the loop happens in the rep opcode which allows for prefetching (meaning that it doesnt destroy the prefetch queue and can even allow for preprocessing).
BTW: for those who commented on my comment porn last time: I made sure to satisfy your cravings ;-)
To those who can't make sense of my command line:
C++ 1m24s
ASM 19s
To those who tell me to call clang with -o<something>:
1) clang removes the call to copy on o3 or o2
2) the result isnt better in o1 (well... one second but that might be due to so many other things, and even if... one second isn't that much)25 -
I Remember what my senior told me once:
"You know you're in the wrong job when you see source code filled with comments written by ur senior dev scolding other devs for code fuckups" -
I hate when I don't comment code and the next week I have to make changes on it and spend 30 minutes just for understand what the code is doing...3
-
I'm a contractor at a product company and today I had the pleasure of working with some jQuery.
A function needed to be called before another function, hard work right?
So I moved the call to the function 3 rows higher, checked it in, set the task as ready for test and started to look for other tasks.
Within a couple of minutes I get a direct message from another dev, let's call him Steve.
Steve wanted me to set the task to ready for code review instead of test, so I did just that and tried to move on.
Some minute or two later Steve contacts me again:
"It would be great if you'd move the comment so it'd be over the call to the function"
Well, I'm not one of those who likes comments... If you need a comment, it's probably not good/readable code. In some cases sure, it might be a complex block coming up.
Sorry, lost my train of thought.
I answered Steve : "Are you sure, I could just remove it instead?"
(for readability S will be Steve and M will be me)
S: Well, it's always good to have comments
M: In this case I think it will be alright.
S: But it's nice to see what the function is doing.
M: I'll do it if you really want me to.
S: It's better to have the comment than to not have it and needing it.
M: Okay then
The name of the function : LoadOrganizationTree()
And this is the comment :
//Load organization tree6 -
Manager : what is "looks good" in code review comment??? You have to be more detailed.
Me in next code review : It is not aesthetically pleasing, but it gets the job done. -
A colleague had to show up for a demo in 10 minutes, and urgently needed to fix some CSS.
I told her the right way would take more than 10 minutes. The quick and dirty way was to add an `!important`.
I made her write a comment:
`// TODO: Fix this hack made for the demo dated blah blah`4 -
Today, I was so certain that all the functionalities were implemented to handle some webhook calls from a third-party service. It's a script I wrote that has been running for 2+ years uninterrupted or without any issues.
We got some "complaints/notices" today that some "special" actions weren't registered, so I thought that the third-party service just didn't send those actions via their webhook. After some research I found a part where they explained that those actions trigger the webhook like any other action etc. So..
First thought: "okay, maybe they implemented that at a later stage" (was not the case)
Second thought: "maybe this is not what the client meant" (it was)
Third thought: "Then it should have been implemented" (it wasn't)
Okay, time to look at the code to see where this could get handled but apparently isn't. All the actions look good, nice, clean handeling etc, nicely documented code (gave the 'past-me' mentally a high-five)..
I scroll further down to that specific action and it was quiet obvious why it didn't work.. I just see an empty function with the comment:
"//TODO: maybe handle this action one day. don't know what this does atm, probably unused.. Will take a look at it next week.."
.. :D
I took my 'high-five' back..I just needed to copy-paste some other code and change 1-2 parameters..1 -
HOW. IN THE WORLD. COULD IT BE SO DIFFICULT TO COMMENT THE CODE I WRITE MYSELF ?
After my first project (you know, the "Working project I made for fun long ago" code everyone did once, but when you look at it again it looks like sorcery and there's no way to understand it ?), I decided that I'd comment almost everything I'd do... But...
When I begin a project, it's fiiiine and I do my comments the way they should be... AND THEN, WHEN DIFFICULTIES ARRIVES AND I START TO BE TIRED (ie : always) THEY START TO INCLUDE INSULTS OR WEIRD JOKES ABOUT THE PROGRAMMING LANGUAGE, MOVIES REFERENCES, AND SOMETIMES THEIR LANGUAGE VARIES. (Like, that project you're doing in English and suddenly there's a comment written in French in the middle of that)
Soo, yeah, even if I do comment my shit now, it isn't more helpful, lol. Maybe I should listen to relaxing music when I code err.
Oh, comments. Damn comments. Someday I'll do those correctly. Maybe.8 -
How to be stupid, be like this idiot who keeps on insisting that electron is a "compiled" and and that is a solution to the "vulnerable" browser app.
By the way this proposed solution is to "hide the ip address displayed on web app" which can be easily done by few teaks on the hosts file instead of developing again. Also mention that everyone in CA uses electron. What an idiot.
Also don't level electron with "compiled" native apps in the desktop.
Translation:
"To all developers out there, there's a way to compile web apps and make it stand alone. We need to upgrade the IT's in the government"22 -
Which one's your favourite IDE 😋?
Intellj vs Eclipse vs Netbeans vs Xcode vs other?😏
Mine is Intellij.25 -
Found this comment in a class I visited today after a few months of writing it.
//todo: Fix this fucking POS hack
I have no idea what POS refers to anymore. FML.4 -
Why do people put so much rbg in to their computers, rather than going for a more solid monochrome look or something?
RGB looks fucking bad, fight me16 -
Stop commenting out code blocks!
Either fix your shit or delete it.
I am open to argue what fixing may mean, as it is perfectly fine to make your broken code not reachable, e.g. via feature flags or skipping certain tests. Yet never ever should you comment those blocks!
So you say you want to keep it for historic reasons? You know, that is why we use version control! If you ever need certain functionality back, you can restore that state.
Each decent IDE also offers a local history where you can even restore code blocks that weren't even pushed or committed. So use that!
Commenting out test cases is a really bad habit, as you have no reminder that you shall restore it.
And no, a TODO and a FIXME won't count as a reminder as you have to actively look for them. And we all know how well that goes, don't we? (One time, I found a typo of a `TDO`. So even with a regular lookup for TODO, stuff will slip.)
Each test suite offers you ways to skip tests if there are valid reasons why they should not fail the build temporary and they offer colorful feedback. Yes, that means that your tests won't be green, but guess what: That's a feature! They shouldn't be.
That yellow is a fine reminder, aka warning!, that you should really fix your shit.
Commented code screams: "I DON'T KNOW WHAT I WAS DOING!" and it confuses the hell out of other developers ("Was this commented because of debugging purposes and should be active again or can I safely delete this!?") and adds verbose crap to the code base.
If you find yourself to be in a place that you comment code a lot, I also argue that your workflow is broken.
When you are using a decent debugger, there shouldn't that much of a need to comment in and out a lot of code in order to reason about your code-base.4 -
/* Spending time writing comments in code because if everything else fails, at least I can write a novel depicting a deteriorating struggle to make up my mind from them */
-
Worked 2 weeks on hunting a memory leak on a product.
Ended up writing object tracker to find the leak(ironically it was in garbage collector). Found the leak and fixed it. It sounds cool but what I pushed was 9 lines commented out 1 line added for 2 weeks work..
Doesn’t feel very fulfilling to work for 2 weeks to comment out few lines. Only silver lining is that I might turn my object tracker into a library for colleagues to use.
P.s: not a linux or windows environment so tools like walgrind aren’t available.2 -
This made my day: (Translation: In reality the earth is a star with 12 spikes and generated by this css script.4
-
Who the f*** came up with the idea to add `com.sun.xml.internal.bind.v2.TODO`
Thanks to a hasty ctrl-space #intellij added this … as import … dafuq2 -
Today, i discovered thus beauty within our legacy code:
// TODO: this is probably the most dirty thing in our product. It needs a model more than anything else
This captions a crappy part of controller code for several years :/ -
I worked a whole year in a company for which I produced 30 software and none of them saw the publication even though they were completed. I was the most productive employee and had a productivity of 428% compared with the other employees.
All because of the constant changes in business strategies.
For a moment I believed to be a pirate ship during a storm. When I was tired of the way they were treating employees, months of backlog payments, unpaid leave or not granted, I quit and I was told to me that I was a bad employee and I was unproductive.
In a month he is left only the designer working. At the moment the company in question is still looking for employees, after more than a year no one wanted to work again. Stupid me.
While I ras looking for another job I did freelance for a month, gaining about five times my earlier pay. -
Ooooops, accidentally reported a comment.. I miss clicked with the "reply" button, and didn't read the dialog
-
Did u know that if a devRant comment gets -1, there is a tendency for a human to follow like a sheep and -1 it too? :D3
-
Thank God for devrant. I am literarily fuming right now. Just removed some redundant (or so it seems ) code last week and already suffering the consequencies. Crazy commenting screwed me up really bad.3
-
Why do I get push notification for comment even when I got the mentioned notificaton of comment on same post and same comment ?2
-
I just don't like copy-pasting the code. can I become a good programmer?
please give honest opinions in the comments.13 -
In the project I'm working on with others, really complex and confusingly programmed, there's a method called "check[...]IsSet". It gives back a string. They went out of their way to write a Javadoc for it and what does it say?
"@return the string"
No, really? I think I could have figured that out by myself! But what's in it, dammit? -
Heh, a review of HHKB Pro 2, think someone missed the point haha.
/Offtopic
Anyone got this keyboard and recommends? I mean, if no one responds I'm buying anyway just nice to hear from devs on it4 -
What is the most unusual use of a programming language comment that you have come across?
I'll start with this one. On the Sinclair ZX81, a REM comment was used to reserve a space, into which you could poke machine code! -
Have you seen those comments which are better than the rants themselves ...
I see myself being forced to ++ the rant, just so people could see the comment :/1 -
In reply to:
https://devrant.com/rants/3957914/...
Okay, we must first establish common ground here. What do we understand about "showing"? I understand you probably mean displaying/rendering, more abstractly: "obtaining". Good, now we move on.
What's the point of a front-end? Well, in the 90's that used to be an easy answer: to share information (not even in a user-friendly way, per se). Web 2.0 comes, interaction with the website. Uh-oh, suddenly we have to start minding the user. Web 3.0 comes, ouch, now the front-end is a mini-backend. Even tougher, more leaks etc. The ARPAnet was a solution, a front-end that they had built in order to facilitate research document-sharing between universities. Later, it became the inter(national) net(work).
First there was SGML to structure the data (it's a way of making it 'pretty' in a lexicographical way) and turn it into information (which is what information is: data with added semantics) and later there was HTML to structure it even further, yet we all know that its function was not prettification, but rather structure. Later came CSS, to make it pretty. With its growing popularity, the web started to be used as a publishing device.
source:
https://w3.org/Style/CSS20/...
If we are to solely display JSON data in a pretty way, we may be limiting ourselves to the scenario of rendering pretty web pages using aesthetic languages such as CSS. We must also understand that if we are only focusing on making a website pretty with little to moderate functionality, we aren't really winning. A good website has to be a winner in all aspects, which is why frameworks came into existence, but.. lmao, let's leave that to another discussion.
Now let me recall back my college days.. front-end.. front-end.. heck, even a headset can be a front-end to a pick-order backend. We must think back to the essence, to the abstract. All other things are just implementations of it (yes, the horrendous thousands of Javascript libraries, lol).
So, my college notes say:
"Presentation layer: this is the UI.
In this layer you ask the middle tier for information, which gets that information from a database, which then goes back to middle tier, back to presentation. In the case of the headset, the operators can confirm an order is ready. This is essentially the presentation tier again: you're getting information from the middle tier and 'presenting it' as it were.
The presentation layer is in essence the question: how do I bring my application data to my end users in a platform-and solution-independent way?"
What's JSON? A way to transport data between the middle tier and the presentation tier. Is that what frontend development is? Displaying it in a pretty way? I don't think it is, because 'pretty' is an extra feature of obtaining and displaying data. Do we always have to display data in a pretty way? Not necessarily. We could write a front-end script (in NodeJS perhaps) that periodically fetches certain information from a middle-tier is serves a more functional role rather than a rendering one.
The prettification of data was a historical consequence of the popularity of the web (which is a front-end) (see second paragraph with link). Since the essence of a front-end is to obtain information from the back-end (with stress on obtaining), its presentation is not necessarily a defining characteristic of it, but rather an optional and solution-dependent aspect, a facet.4 -
<<prev. #wk235 advices>>
~ Study the Error log deeply, Google each line if needed. Don't give up.
~ Learn by doing. Don't just read/watch.
~ Practice breaking down the problem statement first in different components and hierarchies. Don't jump into coding right away.
~ Write some, review some. Don't put off review for later.
~ Even if you don't exactly follow the best security practices - always ensure that your program is safe for use. Especially for user-inputs, etc, pay attention.
~ Never distribute code with passwords/keys written in it.
~ Don't hard code stuff, use Config file, environment variables, etc.
~ Try to automate repetitive stuff like build and deploy etc
~ Save and backup you code.
~ No one knows everything, also, today's knowledge gets outdated tomorrow. Continuous learning is synonymous with this field.
<<next #wk235 advices>>1 -
I don't get annoyed so easily I think.. but when it comes to HTML... why the f*** do the comments have to look like something the cat just shat out?? Why doesn't it support one-line comment?? It's such a struggle to type...2
-
Is there any free software or website one can use where it takes a screenshot or page and you can mark areas on it, then add comments to those areas? (kind of like powerpoint comments, but without the awkward canvas limitation)
Then later the viewer sees instead of huge message bubbles, only those marked areas on top of the screenshot and when he hovers them - sees the comment pop up somewhere.
I remember QA having something like that, but don't remember anything about it. (I think it had a palmtree logo?..)
It would be amazingly useful for clients to just go through screenshots and marking on it "that looks nasty, put ajit pai on it".8 -
People that ask for help on a program I've written...
In the comment section of a completely irrelevant video I made --'2 -
Visiting a site about FOSS and it tells me:
"Note: We are experiencing technical issues with Firefox and our comment system. If you want to leave a comment, please use some other browser."
How about no?! *rage quit*
*popup appears right before leaving*
AARRRRGHHH!! *table flip*5 -
Me editing some other guys code
Me: "Why is there no comments and why is this so spaghetti, what is this even doing, this thing could be done a lot better bla bla"
Others: "Ah yeah nobody has really dared to touch that before. You're the first one to edit it for some time."
*cries* -
I was suprised when I open source of amazon lumberyard forum website and saw reference to another website in comment :D This is the way how it's do it right.
4th row
Link here: https://paulirish.com/2008/...1 -
When you comment on a comment and want to read again what exactly the writer meant and you tap on comment again after reading it adds the username again at the end of your text which is not really a bug but somewhat poorly handled...1
-
Recently took over a freelance project to update an existing app, and this thing is full of comments like "TODO: Remove This" with no context. So hard to work with.
For the love of God, add some context to your comments. Especially if someone else is going to be seeing your code. -
Came across this comment on r/programminghorror/
> We're you talking with my co-worker? He's extremely abrasive, especially when it comes to anyone touching his code because "Now I don't know how it works anymore" -
Trying to figure out the use case for a random stackoverflow question.
Well ...
At least they are honest, I guess? -
I can't post a collab from the web client and I don't have a decent phone atm, anyways, this is an idea, tell me if you have any improvements or if you know of an implementation or would be interested in creating one.
A social network comment system that connects people across fields of interest and aids keeping relevant posts alive for a long time.
The basic principle is this: Every post may identify itself as a child to any number of other posts, or sections in other posts, which then act much like a bidirectional hyperlink between parent and child.
This leads to two unusual results:
1. that comments aren’t only added to posts, but specific paragraphs, sentences or even words.
2. that any comment may receive comments in much the same way the original post did, making comments identical to posts. (they could have their own pages and all).
This is in many ways like Reddit's infinite comment chains. The main difference is that here comments aren’t organized in trees but graphs, which makes it possible to connect related conversations from entirely different groups and times, resulting in a much more open yet concise discourse style with an increased persistence of topics. -
after having to deal with a lot of weird "rewrites" and "refactorings" by co-workers i started to add this comment into the head of my sourcefiles:
You may think you know what the following code does.
But you dont. Trust me.
Fiddle with it, and youll spend many sleepless nights cursing the moment you thought youd be clever enough to "optimize" the code below. Now close this file and go play with something else.
Found this somewhere on the interwebs and since i use it the "refactorings" and "optimizations" of my code stopped nearly completely -
"Anyways trust code that you wrote before but... never rely on that!"
I wrote some code mounts ago, now when I want to refactor it see a bunch of shit, I delete them all and after hours write exactly the previous code!!! just because i don't put some STUPID comments... 😑1 -
Legacy code in java :
boolean recursiveMethod(args){
Int i= 0;
Boolean doublon = false;
For(--whatever the loop--){
If(condition1 && condition2){
If(i++ > 0){
doublon=true;
Return doublon;
}
}
}
[...]
}5 -
If some older employee writes the same code, nobody bats an eye. If a newer employee (with less than 2 years in the company) writes the exact same line, everybody loses their minds (in PR review)...
Not that I give too many fucks generally, but sometimes this partiality is annoying AF.
This causes: https://devrant.com/rants/2263742/...1 -
That moment your pair programmer doesnt comment his code whatsoever, and your'e spending half a day trying to understand what it was he's trying to do😠4
-
I have nothing to "rant" about. Could you write a program to help me out? Better yet, talk about the worst client you have worked for and put it in the comments. ^_^1
-
Most of the code I write are adopted from SO answers and dev blogs, am I a terrible coder or not even one?
-
def longVariableNamesEverywhere(*args):
"""
Not a substitute for docstrings and code comments.
"""
#TODO: insert witty and legible code.
#TODO: learn to read code.
return "Rant and self-deprecation complete."4 -
Maybe I'm late to the game here, but I think the new "Reason for downvote" dialog is pretty wack. I downvote stuff I dislike or have seen before. I report stuff that's offensive...1