Remembering a university lecture

Prof: "What are some other downsides of using polling instead of interrupts?"

Student: "The process has to wait until it gets polled."

Prof: "Exactly. When you click Ctrl+W, you want that tab to be closed immediately. You don't want the system to wait a few seconds for those keys to get polled and risk your mom looking at that tab."

Lecture room 😆😆

Another smartass! Here we go!

Look, I'm an idiot and I'm absolutely aware of it. But you don't get to give an opinion without having the knowledge or skills. I may be young-ish and stupid, but that doesn't mean you're right, or that you know better than me ffs. If I'm down to earth, that doesn't mean you're above me. If you want my respect, then behave yourself. Just because you think you've "schooled me"...doesn't mean you did.

... Aaaaaand those are stuff I'll never say in real life. Gah. I can't lecture people I don't care about, but some do piss me off regardless. And what is with this sharp increase of people pissing me off these day? 🤔 🤔 🤔

Saw this today in the exercise code of a deep learning lecture. These people are doing their PhDs in deep learning 😳

* the snippet has no side effects

Part of a little lecture I gave my boss this week: "... you really should stop taking things so casually and so for granted. ALL of this stuff is not just something you can summarize in a single vague word or phrase like "stuck" or "kick the tires" or whatnot. there's no "magic" to any of this. there's no buttons or knobs you just touch with one finger and stuff magically works. it's all way more complicated than you probably think, ALL the time. And making assumptions will always get us in trouble." (To a tech-illiterate boss who always uses vague verbage like "stick this on the server" and has no idea how anything works.)

According to my university lecture you have clean and good code if every tiny little functionality is split into 5+ files. Gotta have an interface, factory, low level implementation, high level implementation, and at this point I don't even know what purpose the other abstraction levels have. Just end me already...

Sometimes I think of how much great and useful stuff you could learn at an university if they used time efficiently. But instead you spend years mostly just studying theoretical or very abstract topics. Whereas 80%+ of useful knowledge and skills you learn on your own.

Lost my temper at one of our volunteer moderators the other day. We had to do a test using live data, our sysadmin warned him, but not far enough in advance and not really by the right channels. So that was on us. sorry not sorry. But so then he didn't believe us. He must be a geek too cuz he responded with some stupid math problem for me to solve, as if that would prove we work here and aren't hackers or scammers. I replied "how about if i just kick you out of your own group and delete your account, would that convince you?" And so I did. Asshole. Of course I had to apologize later and get a lecture from the boss, but it was kinda worth it.

fuck me.

it's monday and to start in a new project I'm reading a paper my boss once wrote.
It's the worst I ever seen - stop using so much smart words and stop introducing fuckin smart math notations everywhere!!!

That fucker reads like a pretentious science lecture an my poor simple village brain doesn't like it

Is this normal to get mails like this when we mention we have an offer ?

I am tempted to reply "Thank you for the free moral science lecture".

Recently I've had a lot of realistic dreams and it's awful. For example, yesterday I dreamed that I have a SoftEng lecture on Monday at 9am. The day before I dreamed that Russia defeated Ukraine and are now neighbors with Hungary. On both occasions I was later convinced that the memory fragments were true until I either received conflicting news or some unrelated trigger reminded me of the later, unrealistic parts of the dream.

I can sort of deal with the possibility that my current life is a dream and I'll eventually wake up and start over from an unspecified morning, but the possibility that while living in reality an arbitrary subset of my memories comes from dreams is much worse

Summary of My Experience With Recruiters

1. They do everything until they get a phone talk. They also go cold turkey if they don’t have what you want, no politeness if you are not useful to them.

2. They are OK with your highball salary range at first
3. Once they got that you are hireable, they show their true nature

3a. Trying to lower my forever salary expectation to guarantee an offer and their one time bonus

3b. They scare you implying I would be fired from job anyways, if I don’t like some aspects of the current job

3c. They call you multiple times a week with no scheduling beforehand

3d. They lecture me on why salary shouldn’t be a big reason for job change(bitch don’t even…)

3e. They say shit like I want you to get this job(dude, you say that to every job seeker)

I will add more if I remember. What are your other bad experiences

One of the more memorable friends through coding is a guy I met at 9am at what had to be an early lecture with 150+ students. We were both following it as part of a minor but the only ones there: we apparently didn't get the message that it was cancelled because we were no majors...
We decided to just work on the group assignment because why not and became friends.
Little did we know that we had already met dozens of times (but never really talked) the two years before as we are both members of the same students association, only strengthening the bond!

Sometimes not receiving a notice of cancellation is not that bad...

Ayo going education mode tomorrow - hittin the books, going to the grand lecture hall