Still a Youth
Well-Known Traveler
- Joined
- Nov 12, 2021
- Messages
- 1,226
- Reaction score
- 3,142
- Awards
- 247
This thread has been viewed 2565 times.
That's actually depressing tbh. It's like an extension of parents. Can't do a bunch of stuff because of what they say and when u don't wanna do something it's also an excuse.They never have time for anything anymore outside of 24/7 supervision of their spouse and kids. "Sorry, I can't talk for too long, my wife is tired tonight."
That's actually depressing tbh. It's like an extension of parents. Can't do a bunch of stuff because of what they say and when u don't wanna do something it's also an excuse.
I feel like if I want a relationship that isn't like this I've gotta be super careful. And that's a whole thing since it isn't easy to find anyone in the first place. Recently I was thinking about helicopter mums (can be dads too). It's like somehow they lose interest in everything in their life and decide their whole purpose is getting their child the best chance in life whilst giving them everything. And then the schools get to use them for free volunteering.
Also I have a 6 year old sister and my dad and step mum are in group chats for their respective gender of parents from her school. The dads one they send random sexual stuff (idk maybe funny maybe not) and the mums complain about their husbands.
Sometimes I don't get it, but in another way I do. Everyone hates their life but everyone tries to convince you to do what they do. I suppose there's some bad shit in us trying to use anyone to validate ourselves.
This must be why every "what's a good algorithm for (x)?" on Stackoverflow is answered by "just use (library) bro". Yeah, nevermind that I just need to do one simple thing, want to learn how something works, or just don't want to include yet another goddamn dependency so people can use my code with less hassle. It's especially bad with C++, every other answer is "YOOZ BOOST".From various people but especially university professors: "Understanding <topic> is a waste of time. Just use <software package>. You'll never get anything done otherwise," often followed by, "understanding <software package> is a waste of time. Just use <more fashionable software package>. You'll never get anything done otherwise."
Fair enough, and more power to you. I'm firmly of the belief that people who don't want to have kids don't need to justify their choices. Honestly though the thing that irks me is that, at least where I am, the number of under-40's who are blatant child hating anti-natalists vastly outnumber those who are condescending about not wanting to have kids. You do not seem to be one of those people so I won't lecture you as an individual on it, but my SO and I have our shit together and want to eventually have kids someday. It's frankly infuriating when immature people from our past hear that and say things like "Ew why would you want to ruin your own lives like that?" completely unironically. The choice to have kids (or not to) is probably the most personal decision you'll ever make, and as long as the decision is made with clear eyes and a level head it should be respected by both sides.Anyone who wants to start a family has my full support, but don't try to push that on me.
That software one is so true, especially in the job, there's no time to learn how things are done. Especially if there's a deadline to meet.From various people but especially university professors: "Understanding <topic> is a waste of time. Just use <software package>. You'll never get anything done otherwise," often followed by, "understanding <software package> is a waste of time. Just use <more fashionable software package>. You'll never get anything done otherwise."
From my dad: "If you don't go to <publicly funded summer program for 10-13 year-olds> then you'll never achieve anything."
I've probably heard dumber things, but these come to mind as the worst right now.
In my experience, if you want to actually learn anything about computers (outside of a classroom) then you need to use books and technical documentation. StackOverflow is ok for basic information (e.g., explanations of obscure compiler errors), but you usually have to read all of the answers. Sometimes you even need to read all of the comments to get good information.This must be why every "what's a good algorithm for (x)?" on Stackoverflow is answered by "just use (library) bro". Yeah, nevermind that I just need to do one simple thing, want to learn how something works, or just don't want to include yet another goddamn dependency so people can use my code with less hassle. It's especially bad with C++, every other answer is "YOOZ BOOST".
I took a course called Microprocessor Assembly Languages (which is a bad title because it was really just about microprocessors and we only used 32-bit ARM assembly). I got a lot out of it. Even if you're not programming specific microprocessors directly, understanding how they work at a basic level is pretty useful.Now, you can go too far in the other direction. I took a class on Assembly in college, and the whole time I was thinking "this is way too deep for anything I'll ever do."
I don't want to derail the thread (any more than I already have) by just talking about comp sci college courses, but I'm glad you got some use out of that crazy low level stuff. Every job is different, and maybe I've just been lucky that I've never needed it.In my experience, if you want to actually learn anything about computers (outside of a classroom) then you need to use books and technical documentation. StackOverflow is ok for basic information (e.g., explanations of obscure compiler errors), but you usually have to read all of the answers. Sometimes you even need to read all of the comments to get good information.
I took a course called Microprocessor Assembly Languages (which is a bad title because it was really just about microprocessors and we only used 32-bit ARM assembly). I got a lot out of it. Even if you're not programming specific microprocessors directly, understanding how they work at a basic level is pretty useful.
Generally, my view is that you should try to understand as much as you can manage about the system you're working with. It's definitely easier and usually faster to just plug in an existing solution. In my opinion, building the expertise is more valuable though. You absolutely have to draw the line somewhere (e.g., I'm not going to get a PhD in applied physics just so I can understand integrated circuits better than I currently do). I just think that most of the time people are drawing the line in the wrong place.
Speaking of bad computer advice, I think the famous, "if you want to set off and go develop some grand new thing, you don't need millions of dollars of capitalization. You need enough pizza and Diet Coke to stick in your refrigerator, a cheap PC to work on, and the dedication to go through with it," is completely out of touch.
ok but fake it till you make it mentality works surprisingly well"Be confident."