Do all the things like ++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatarSign Up
Get a devDuck
Rubber duck debugging has never been so cute! Get your favorite coding language devDuckBuy Now
Search - "old thread"
Imagine, you get employed to restart a software project. They tell you, but first we should get this old software running. It's 'almost finished'.
A WPF application running on a soc ... with a 10" touchscreen on win10, a embedded solution, to control a machine, which has been already sold to customers. You think, 'ok, WTF, why is this happening'?
You open the old software - it crashes immediately.
You open it again but now you are so clever to copy an xml file manually to the root folder and see all of it's beauty for the first time (after waiting for the freezed GUI to become responsive):
* a static logo of the company, taking about 1/5 of the screen horizontally
* circle buttons
* and a navigation interface made in the early 90's from a child
So you click a button and - it crashes.
You restart the software.
You type something like 'abc' in a 'numberfield' - it crashes.
OK ... now you start the application again and try to navigate to another view - and? of course it crashes again.
You are excited to finally open the source code of this masterpiece.
Thank you jesus, the 'dev' who did this, didn't forget to write every business logic in the code behind of the views.
He even managed to put 6 views into one and put all their logig in the code behind!
He doesn't know what binding is or a pattern like MVVM.
But hey, there is also no validation of anything, not even checks for null.
He was so clever to use the GUI as his place to save data and there is a lot of parsing going on here, every time a value changes.
A thread must be something he never heard about - so thats why the GUI always freezes.
You tell them: It would be faster to rewrite the whole thing, because you wouldn't call it even an alpha. Nobody listenes.
Time passes by, new features must be implemented in this abomination, you try to make the cripple walk and everyone keeps asking: 'When we can start the new software?' and the guy who wrote this piece of shit in the first place, tries to give you good advice in coding and is telling you again: 'It was almost finished.' *facepalm*
And you? You would like to do him and humanity a big favour by hiting him hard in the face and breaking his hands, so he can never lay a hand on any keyboard again, to produce something no one serious would ever call code.4
Find super interesting forum thread from 2015 with intelligent discussion about deep technical stuff.
Creating forum account, thinking about contributing to ongoing discussion with code samples, findings, hypotheses, and some open questions.
Browse to last post, is from late 2016, from moderator:
READ FORUM RULES DO NOT POST IN OLD THREADS LOCKING THIS
Me: 😡😤😠 WHO THE FUCK CAME UP WITH THE SHITRULE THAT A DISCUSSION HAS AN EXPIRATION DATE? IF I COULD REACH THROUGH THE SCREEN RIGHT INTO 2016, I'D PUNCH YOU THROUGH THE ROOF OF YOUR MOTHER'S BASEMENT. NO ONE LOVES YOU, YOU USELESS MOTHERFUCKING CUNT OF A MODERATOR.3
Imac - brand new <16hrs used: Disk error, probably needs to return to apple
iPhone <6 months old: loses cover
iPhone case 2hours of use: loses color
Macbook Pro 2017: randomly shuts down...
Mac mini: CPU halted error
Other iMac (old one): Thread error...
Apple, what the f is going on??? Software problems with root etc. But now, what the f!!9
Just did my first JobIntentService on Android. Hoo, boy.
The problem: I need to send a network request.
The issue: Android.
Of course, you can't do network on the main thread. That's silly in any application. Android really does try to punish you, though. The Android lifecycle can really fuck you over here. Imagine a long-running network operation, like 15 seconds. Plenty of time for the user to do something silly, like rotate the screen.
If you opened up a good old new Thread from Java, you'd get a crash because of a screen rotation. Same thing with Android's AsyncTask, which is the top answer on StackOverflow. AsyncTask is made for things that will take no longer than a few seconds (less than 5!). Network, especially cell network, can take longer.
So the solution? Create a JobIntentService class. It's a service, it will run in the background. You need to register it in your Android Manifest and ask for a new permission (wake lock). You need to implement another class for the receiver, and then you need to go to your activity and implement the receiver interface you just wrote.
Just. For. A. Network. Request!
And as far as I'm aware, this isn't even that bad considering the rest of Android's bullshit.
What a headache!8
Ah, the old locked up non-gui thread. Bastard gets me every time. My monkey brain says "Button still work, so no infinite loop". Oh, but there DO be infinite loop.
Ninjaaaaaaaaaaaaaaaaa i fucking hate you you fucking piece of useless crap. When i say you build with one thread build it with one fucking damn thread and not the entire damn CPU.
See good old make can understand it and does as i say him to do.
Why cant you be like him and listen to what i tell you to do ?
Nooooo you just have to replace the entire fucking arguments i gave you with your fucking own just for fucking fun and make me fucking mad at you.
You really are fucking useless piece of crap but other then android build you are pretty decent.
But still piece of crap for android.
Not to say that build takes 2 hours longer with you.
Im fucking lucky to be building 7.1 android where i can turn you fucking off since i cant do that with 8.1 since google thinks you are fucking better.
@dfox New excellent algo sort makes lots of old threads bumb which means better notifications is suddenly more important.
I'm wishing for notifications grouped per thread and with a line or two of the rant/comment the notifications is about.
I fucking hate Visual Studio!
Don't get me wrong, from time to time I actually enjoy it but not today.
It all went south when I tried to add a new handler to an fucking old asp.net webpage. I had the access the 'Range' headed to stream bits of audio and video files to the client. It was working absolutely fine for the first hour and a half, after that point the fun started...
VS decided that my source code and the binaries won't match anymore. Everytime I tried to add a fucking breakpoint or debug this cunt of an error it would just refuse
The worst part that made me go apeshit was when I finally got a breakpoint and the exception. Some unknown fucking system dll just kept on killing my thread without a proper error message because it's optimized to the fucking moon and back!
Any ideas from the devs here on what's going on and how the fuck I can fix this?6
Me: *pastes error message into search engine* && *clicks first result*
First Result: Hey I have a problem with *this error*
Same here, anybody know how to fix it?
This has been irritating me for the past 2 minutes, somebody please help
Me: *replies "same" on a two year old thread*
What's wrong with reviving/bumping an old thread on a forum? It seems way more efficient to me to continue on one central thread. I hate common rules like "don't post in a thread that's a year old, start a new one". Why not keep the conversation in one place? What am I missing?
Isn't this already how we (properly) do email threads? I always go back to find the last email when I send a follow up to avoid breaking into two different threads with two different sets of replies.5
Sometimes I hate StackOverflow's review because I tend to comment and the post turns out to be 5yo top question with inf. amount of comments.
And there I come, the captain obvious, bumping an old thread because the review told you it's 2hours old or something.
I need advice: study 4th year (Bachelor's) or work?
Thought I saw a similar thread a while back but can't find it in search right now.
21 years old, end of this year I'll graduate with a diploma (3rd year). I have one option of university here because they're the only one that offer my course (IT instead of CompSci like the others). Their administration and general status is not stable (see my earlier rant or Google CPUT protests in the news). Couple this with a deep desire to move out (housemates and drama) and wanting to keep working instead of going back to study.
Thoughts? My current best bet I think is to hedge my bets and apply anyway, then if I don't want to study next year I won't. Still seeking opinions though. Local market (mostly recruiters) values qualification too much. Planning on moving away anyway but will need a job to hold me over until then.