Title before edit: I hate programming, why did i choose this field
TL;DR: Stupid mistake, made by hours waste.
Basically, I was extracting date from the SQL db, and it was not displaying. I tried everything, heck I even went to chatgpt, and copilot. Two and half hours of trying every single thing under the sun, you know what was the issue?
SELECT task, status, id FROM mainWorkSpace WHERE user_id = @user_id
I FUCKING FORGOT TO ADD ‘date’ TO THE DAMN QUERY. TWO AND HALF HOURS. I was like, “Ain’t no way.” as I scrolled up to the query and there it was, a slap in the face, and you know what was the fix?
SELECT task, status, date, id FROM mainWorkSpace WHERE user_id = @user_id
Moral of the story, don’t become a programmer, become a professional cat herder instead.
You didn’t add the date field to your query and couldn’t work out why it didn’t return the missing field for over 2 hours?
Perhaps SQL isn’t for you as things get waaaaay more finicky than that.
You’ve never made a silly mistake where you “can’t see the forest for the trees”?
It happens to the best of us
One time I’ve been trying to force UE5 to let me edit TArray<TPair>, an hour later I realized I could just use TMap
Yes of course, but it’s not the sort of thing I’d make a rant post criticising the entirety of programming about.
It’s like going to a mathematics forum and declaring “Guyz I forgot to carry a 1, screw Maths.”
The title was an over exaggeration on my part
Because developers are all logical and don’t EVER show anger at the systems they’re working on…. Hahahaha…
I mean I personally wouldn’t post about it, but I’d probably rant over lunch at my stupidity…
The best devs Ive worked with are all “barn cats”. They yell, they challenge, they curse, they gesticulate, but they never offend.
(The f’n Workplace Sensitivity thing I just took outlawed so many behaviours that I know would exclude every superhero I know. What’s happened to the industry?)
There’s a difference between ranting to your coworkers at lunch about a stupid mistake and typing out a full rage essay.
Imagine the state of the sub if we all did that… Wait…
This “full on rage essay” is nine sentences, including the tl;dr and the sentence fragments. There’s really not a big difference between telling your coworkers a story like this and posting about it on social media.
Did you read it before the edits? If it’s written like that I think I’m entitled to exaggerate back slightly to make a point by calling it a rage essay.
Anywho I wouldn’t choose to rant like this to my coworkers or online. A quick 🤦 in chat usually does the trick.
I read it a few hours ago. Was it substantially longer before?
Not substantially, it had a different title and was toned down.
I withdraw the word essay and apologise for any rudeness.
Have a good one.
deleted by creator
No, He’s just trying to excuse his own emotional reaction.
Oh I’m not encouraging it, personally I just ignore the rants like that….
But at the same time, I can identify the emotion that drew the person to do it.
Ah yes here you are successfully ignoring it.
Might not be encouraging it but you seem to be defending it.
I ignored OP’s statements, not yours.
You’ll find I replied to you and not them, but I appreciate your condescension in the midst of being wrong.
Ranting about problem you had and being dramatic about it? No problem, I get it. I’m here to be supportive of your struggles. I’ll absolutely defend someone that is being dramatic over their own mistakes, we’re all our own biggest critics. Beyond that, I’ll ignore it and let them get through their own emotions.
Feeling the need to judge someone over it? Yeah, YTA here and you’ll find that coworkers don’t like you for it. It’s unpleasant, and unnecessary.
Do you enjoy it when people point out your faults and say “maybe the tech world isn’t for you?”
…… but you’re not going to see it that way at all. You’ll create some meaningless “but it’s different” argument because you feel the need to defend your actions rather than reflect on them.
Have a nice day, I’m done.
Wow ok chill.
The title of this post was “I hate programming, why did I choose this field”.
I responded suggesting maybe OP isn’t suited to SQL in particular. There are plenty of other languages to learn that they might pick up quicker if they are struggling with SELECTs.
You may think you’re joking, but as a Maths teacher I can tell you I have seen a lot of posts where someone makes a mistake with their signs, then uses their wrong answer to declare “The rules of Maths are wrong! Look - different answer!”. Yeah umm, try working on getting your arithmetic right first before claiming to have “proved” something. 😂
Whooosh
Seriously. If this broke him it gets so much worse… but honestly op, this is how you learn what to do and what not to.
I know that, my anger has manifested this post, and I shouldn’t have criticized the entire field
I think anyone who’s been in the field for long enough knows you weren’t really slamming all of it. Beaking off is totally okay.
Fair play. SQL is pretty different from traditional programming and errors often aren’t very descriptive.
You’ll need to get very familiar with fields you have included or not in your queries when using more advanced stuff like group functions as including or excluding them can alter the number of rows returned.
You don’t know the circumstances. They might have only seen the query results after several processing steps…
You are correct I don’t know the circumstances so all we can go on is what OP wrote…
it’s indeed a new language for me and I haven’t developed that ability to know where the bug is happening but I am going to get there.
Assuming you’re coming from a linear programming and OOP background, then data (incl. SQL) kinda sucks because it’s not always clear how to apply existing concepts. But, doing so is absolutely critical to success, perhaps more so than in most OOP environments. Your post isn’t funny to me because I’d be laughing at you, not with you.
If a variable is fucked, the first questions you should answer are, “Where’d it come from?” and “What’s its value along the way?”. That looks a lot different in Python than SQL. But, the troubleshooting concept is the same.
If object definitions were replaced by table/query definitions in planning then you’d probably not have made the initial error. Again, it looks different. But, the concept is the same.
That’s correct, I have done a lot of OOP in Java and C#, and the internship I’m doing is with C# and ASP.Net.
You see, I wasn’t thinking clearly at the time, wasn’t looking at the right place, and like the post says, I’ve finally looked at the right place and made me feel frustrated. The frustration was at myself not at programming.
Yeah don’t beat yourself up - when you are new to SQL it fucking let’s you know.
It’s easy to get distracted thinking about all the ways shit fits together., where you could have just gone wrong. And now, next time, you’ll know.