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
-
When you are doing dijkstra every 5 fucking second trying to pass the guy in front of you while walking.
4 -
Poor Dijkstra is probably crying in his grave because my professor calls him "digest-tra" 😢 feelsbadman8
-
!rant
After reading the wiki page over and over, I was finally able to implement Dijkstra's algorithm 😃4 -
Actually the worst fucking developer experience is meeting those all knowing people who think they know everything but actually they even don’t know how the fucking tools they’re using every day are written and how they work.
Those people that think when they installed library it should do everything how they imagined to and don’t fucking bother to debug problems and create pull requests if it’s fucking buggy.
Those fucking ranters who moan about something they don’t understand.
Those fuckers who think if they understood what A*, Dijkstra, graph algorithm is they’re smarter then others.
No you fuckers you’re dumb as fuck cause instead of explaining it to someone you just blame people for not knowing “obvious shit”.
All those fucking ignorants I am fucking writing about you.
You either start support each other or fuck you people.7 -
"If debugging is the process of removing software bugs, then programming must be the process of putting them in." - E. W. Dijkstra3
-
When you spend a couple of hours considering how to change your implementation of Dijkstra's algorithm to be directional only to realise it already was
Fuck!
Self.setIntelligence(-1)3 -
Dammit Peter, just make a damn decision and *stick with it*. This is explicitly your choice - I don't care whether we go with framework x, framework y, or framework z. I'm comfortable with each of them. So's everyone else on the team.
But for the love of Dijkstra, please do the research, cement it in place & stop changing your mind in every bloody standup because of another forum post you've seen where someone had an unrelated issue with x framework 2 years ago. -
"The question of whether computers can think is like the question of whether submarines can swim." - Edsger W. Dijkstra1
-
We need to separate concerns. Too many CS courses skip over theory and teach outdated tools and technologies, often those of a sponsor who is failing in the market.
Computer Science is supposed to be about the science and formalisms of computation. The job of programming is Software Engineering. A few colleges have SE degrees, but too few.
No one understands anymore the likes of Knuth, McCarthy, Dijkstra, and Hoare. I'm willing to bet that most of you have never read any of their work. Few people really understand their impact on the tools we use today or the importance of their work. CS courses should teach that and expand on it so we can get more huge leaps in tools and concepts.
But we also need Software Engineering to teach students current tools and the latest paradigms.
CS, as it is, doesn't do that. -
Oh BASIC night, the LEDs are brightly glinting;
It is the night of the dear GOSUB’s birth!
Long lay the world in sin and error printing,
Till you appeared and the RAM felt its worth.
Shiver of fear, line numbers do inspire,
For yonder breaks a mostly harmless GOTO.
Fall on your bits, O hear the Visual voices!
O BASIC divine, O BASIC where GOTO was born!
O BASIC, O Holy BASIC, O BASIC, you’re mine!
Some want to say, “GOTO is harmful always,”
But what of them, in their post-modern world.
We PRINT the truth, in the line-numbered goodness,
But Dijkstra appeared, and the faith, it was lost.
A thrill of hope, when .NET BASIC announces,
But Visual BASIC, what kind of thing are you?
Fall on your GUI, O see the old line numbers!
Behold BASICA, O BASIC when DOS was born!
O numbers, O lines, spaghetti divine!
Source: http://changelog.complete.org/archi...2 -
Dijkstra said if debugging it's the art of remove the bugs from the code, programming must be the art of putting bugs in the code.1
-
Just implemented A* and Dijkstra to get into pathfinding with graphs. Really hyped about this! TIL that Dijkstra is perfect to find the quickest subway route in my city 😏2
-
Found in kernel/sched.c in Linux 1.2:
The "confuse_gcc" goto is used only to get better assembly code..
Dijkstra probably hates me.
https://git.kernel.org/pub/scm/...3 -
“The question of whether a computer can think is no more interesting than the question of whether a submarine can swim.” (Edsger W. Dijkstra)
-
Dijkstra 1988: "Unfathomed misunderstanding is further revealed by the term 'software maintenance', as a result of which many people continue to believe that programs —and even programming languages themselves— are subject to wear and tear. Your car needs maintenance too, doesn't it?"
npm 2018: "Naaaah!" -
I can understand why in technical interviews they use those algorithmic questions. It's an incredibly short period of time to assess someone's coding capabilities. BUT can't we find a better way to do it? I mean, I've never implemented dijkstra in a work environment, and I had never heard of someone that faces those kind of problems in a normal day of work.
I may be judging by my limited information, but wouldn't be more useful to actually ask to solve a more plausible problem?
For example, create a microservice that implements this API, send us the GitHub link and the API url.
¯\_(ツ)_/¯1 -
Theorem 2.71 All software is shit.
Corollary 3.14 So stop the braindead OS wars. All OS are shit, too.
Proof. The only software that can stay beautiful and clean is software that is never used. Maybe if you are Dijkstra or live in a Haskellian world, you might come away with it, but for the rest of us our artifacts have to interact with other artifacts or are build upon strange historically grown systems, they have to deal with users who will put it to creative use.. and in the process we also actually might have to alter some state.
Or put another way: code is a social construct. Like science are the beliefs and superstitions grown by a scientific community, software is the montainous dunghill produced by our laborious efforts to make shit even work. Of course this only piles the stack higher and higher until you can already smell it from the moon.
Top Tags
Weekly Rant
View