Joined devRant on 9/6/2016
Do all the things like ++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatarSign Up
From the creators of devRant, Pipeless lets you power real-time personalized recommendations and activity feeds using a simple APILearn More
When you come back from your coffee break, and realize you just wrote 40 lines of Python, but the app you're working in was written in NodeJS. I really need this coffee.3
Me: flutter upgrade
*15 minutes later*
Me: cool all done!
Me: flutter run
Flutter: gotta redownload that successfully installed update all over again because fuck you!
*cries in corner*5
Get a comment about do I know it is working? My answer, debugging. They respond back with a question about debugging and some details I totally didn’t read.
Well, that was the bug. Chrome debugger was showing a message I didn’t understand. So they answered my problem perfectly.
But before realizing he answered my issue, I blew up. Of course I know what is going on. The debugger is showing me....did you even run my example?
I almost felt like giving up as a developer. Here is this awesome guy, solving my issue, and some dumbass like me has to be frustrated. Now he won’t respond to take a bounty he so awesomely deserves.
I’m still a dev. I just don’t feel so professional anymore...
Have u heard about ear infarction?
Which makes one of your ears deaf?
Aaaah! I got one!
Tommorow must go to the doc then he injects inside my ear (hope it is less painful then i think)
Wish me luck ! Hope I can hear things as before soon24
I kid you not, it's been impossible to find a rubber duck, so I had to make my own. Yes, his head is wonky, it's intentional, I wanted him to match me 😁19
I was going to work on a group project in C++ today. I thought to myself, how hard can it be to git clone it, open it in Visual Studio and run it. Boy was I wrong.
VS opened it fine, but when I tried to run it I got over 300 errors about missing headers, including windows.h. turns out I didn't have the correct version of Windows SDK installed. Installation (and download) took over 2 hours.
When it finally installed, the linker started complaining about headers not existing, even though I could see they did in fact exist. After 20 minutes of googling I finally got VS to recognize the headers as existing.
Then I wanted to start working on my part of the project. So I made new .h and .cpp files with namespaces and classes. Except I accidentally gave a variable a value in the header file, and apparently that's not allowed (because of course it's not). So I moved the assignment into the implementation file.
Apparently I can't do that either, because I have to tell what type that variable is, even though I already did it in the header. But when I do add the type in .cpp files it complains about a redefinition if this variable.
After almost 5 hours, I have wrote like 20 lines of code that doesn't even compile.
I give up. I'm going to bed. Maybe tommorow I'll manage to force VS to work2
I was cleaning up my hard drive and deleted some old directories.
I was notified that my backup just started and wanted to look how far along it was.
However, instead of 'ls -l /mnt/DATA/Backup' my shitpile of muscle memory typed 'rm -rf /mnt/DATA/Backup'... That's when my harddrive suddenly had 750GB of free space and I decided that I probably need some sleep.
Before any of y'all wanna lecture me on off-site backups, funny thing: Today I implemented a new daily backup routine (praised be borg) and therefore deleted my somewhat chaotic Backups on my NAS "Because if shit hits the fan, I still have my local Backup"2
Today my friend discovered a mechanical calculator at school, we were playing around with it for >1hour, very cool9
I was watching a video by Karl Smallwood about the size of Superman's package when I noticed the YouTube algorithm decided that only three videos were similar.
It just seemed strange6
i was browsing tinder and there was a girl with a bio status that said
"if you are in IT, swipe left, get the fuck away from me"64
Dear assholes of the internet. Next time you publish an article/tutorial/story etc, PUT THE FUCKING PUBLICATION DATE AT THE TOP.
I don’t care about your need to be minimalist, FUCK YOU, INCLUDE THE DATE.18
few years back,I wanted to be become supercar designer or weapon designer.
Due low grade in 12th.I got admission in computer science instead of mechanical.
c was introduced in 1st sem.
Score well in first year.
college offer me to change my field cs -> mechanical
4 year later (now)
1) due to health
2) financial issues
happy to be full stack developer.
still like cars and weapons but choosed cs as my real career.16
The worst career choice I ever made was walking away from a six figure salary software development job with benefits to focus on the small startup I co-founded just a few years earlier. My wife and I had two small children at the time and my wife was also nearly 8 months pregnant with our third. It resulted in an approximate 70% reduction in income, prematurely cashed out 401k and loss of existing health insurance.
To be fair, it was also simultaneously the best career choice I ever made. Three years later I make more now than I originally walked away from. The raw roads of stress, anger, fear and complete uncertainty have aged both me and my wife at an accelerated rate but we have grown closer to each other than we would otherwise be. We have relied on each other, and she has been unbelievably supportive with all the late nights and required traveling. We discovered what we are capable of. In one day it will be October. In one day it will be the month that we finally pay off our last batch of credit card debt that resulted from that career choice.
I cannot recommend following in our footsteps as from where I’m sitting there are much better, more calculated ways of going about it. Logically, what we did was beyond stupid. Luckily for us, we were still young enough to not grasp the full magnitude of stupidity and we also refused to fail. It’s also crucial to have stellar business partners who are just as crazy and just as determined. We have all labored tremendously and we have each played critical roles in our success. The hard times of fear and uncertainty aren’t over. I don’t think they will ever be, to be honest. But, it sure has been one hell of a ride. I wouldn’t change a thing.18
Anyone else notice this trend:
1. Don't go to uni / drop out (who needs education).
2. Get a job in IT, it pays well (who cares you don't have a structured logic).
3. Learn need-to-know stuff only (I only need to know my code).
4. Tell others they should get into programming, it's not that hard.
5. Get asked about the workings of a computer, but that's not in your domain of work. "I only code".
Millennial much ?14
devRant is just like developers democracy
devRant is an APP "of the DEVELOPERS" , by the DEVELOPERS, and for the DEVELOPERS6
If you see someone coding at mcdonalds, starbucks etc.
"Excuse me, would you like a fork for that spaghetti"14
I just can't learn dance moves, every tutorial is like 1, 2, 3, 4 ... 1, 2, 3, 4 where's the freeken first step?5
When I hear, "master/slave" I don't think about terminology and syntax for a programming language I dislike because of its silly functional indent requirements. I think of jumper settings on IDE hard disks in the '90s. Primary master, secondary master, primary slave, secondary slave.2
Okay, story time.
This rant is about the many mistakes I made at the time, specifically the biggest – but not the first – of which: publishing some preliminary results very early on.
So I posted a sarcastic question to the Software Engineering Stack Exchange, which was originally worded differently to reflect my frustration, but was later edited by mods to be more serious.
You can see the responses for yourself here: https://goo.gl/poHKpK
Most of the serious answers were along the lines of "multithreading is hard". The top voted response started with this statement: "1) Multithreading is extremely hard, and unfortunately the way you've presented this idea so far implies you're severely underestimating how hard it is."
While I'll admit that my presentation was initially lacking, I later made an entire page to explain the synchronisation mechanism in place, and you can read more about it here, if you're interested:
But what really shocked me was that I had never understood the mindset that all the naysayers adopted until I read that response.
Because the bottom-line of that entire response is an argument: an argument against change.
Nexus does not and will not hold your hand. It will not repeat Node's mistakes and give you nice ways to shoot yourself in the foot later, like `process.on('uncaughtException', ...)` for a catch-all global error handling solution.
No, an uncaught exception will be dealt with like any other self-respecting language: by not ignoring the problem and pretending it doesn't exist. If you write bad code, your program will crash, and you can't rectify a bug in your code by ignoring its presence entirely and using duct tape to scrape something together.
Back on the topic of multithreading, though. Multithreading is known to be hard, that's true. But how do you deal with a difficult solution? You simplify it and break it down, not just disregard it completely; because multithreading has its great advantages, too.
Like, how about we talk performance?
How about distributed algorithms that don't waste 40% of their computing power on agent communication and pointless overhead (like the serialisation/deserialisation of messages across the execution boundary for every single call)?
How about vertical scaling without forking the entire address space (and thus multiplying your application's memory consumption by the number of cores you wish to use)?
Some will say that the performance gains aren't worth the risk. That the possibility of race conditions and deadlocks aren't worth it.
That's the point of cooperative multithreading. It is a way to smartly work around these issues.
If you use promises, they will execute in parallel, to the best of the scheduler's abilities, and if you chain them then they will run consecutively as planned according to their dependency graph.
If your code doesn't access global variables or shared closure variables, or your promises only deal with their provided inputs without side-effects, then no contention will *ever* occur.
If you only read and never modify globals, no contention will ever occur.
Are you seeing the same trend I'm seeing?
When someone says we shouldn't use multithreading because it's hard, do you know what I like to say to that?
"To multithread, you need a pair."18
I've been struggling with the network I set up for my bachelor thesis for weeks. Today I figured out it was all caused by STP which disabled connections that I tried to use. Disabling STP solved all my problems.
The relieve is strong
We had a major core router hardware failure in our LA datacenter today and every one of our services has been down since 6am, including all production servers. We have about 15,000 sites down across our entire platform. Our manager came over and told us to just go home because we need to replace the hardware and the process is expected to take all day, and we can't do any work until then because all the production servers are down. So you could say that it's been a pretty easy Friday so far! I'm headed home to play Spider-Man2
I'm using C++ for machine learning purposes using TensorFlow and OpenCV (rip Python, you are too slow 😭)
What are you using C++ for? 😁19
About 10 years ago my wife and I were buying a house. We found out late that we needed a lot more cash than we had previously thought we needed, and the deadline to deliver it was just a few days away. After returning home from my full-time gig at about 6pm, I took a break for a bit and then worked all night on a job for a client to make up the extra money. When 7am rolled around I had just finished up. Then I went back to work at my full-time job, and later met with the client to present my work. It was roughly 27 hours at a keyboard for me. That effort made it possible for us to successfully buy our first home. If you want something badly enough, make it happen!7