What's the downside of having a "high tech" classroom with Bose speakers and a mid tier PC you say?

Hackers

So back in highschool we used to have these fancy "corporate" classrooms with speakers, PC and projector setup (plus really comfy chairs). Classrooms were organized in triads next to each other so we usually knew when classes where taking place next to us.

One day I decided to fuck around with teachers, I waited until he/she started class and I remotely blasted music or porn sounds on the third empty classroom and waited until the angry teacher rushed to the classroom then...silence...nothing but an empty classroom.

One day one of the teachers was so pissed because I orchestrated a Vivaldi concert with the 3 classrooms he rushed into ours and took a friend of mine who he had a personal grudge against, I kinda felt bad but not so much after my mate told me that was genius and that we should do it again.

You think a junior dev pushing his code onto a production server is bad? Wait till you have that admin who is illegally mining Bitcoin on your production server. 😂

I went for a Cyber Security conference today with one of managers and this was one of the life experiences some of the speakers shared.

Udemy courses are targeted at ABSOLUTE beginners. It's excruciating to pull through and finish the course "just because". And some of these courses are jam-packed with 30-60 hours just for them to appear legit, but the reality is the value you get could be packed to 3-5 hours.

You're better off just searching for or watching for the things that you need on Google or YouTube.

You'll learn more when building the actual stuff. Yes, it's good to go for the documentation. Just scratch the "Getting Started" section and then start building what you want to build already. Don't read the entire documentation from cover to cover for the sake of reading it. You won't retain everything anyway. Use it as a reference. You'll gain wisdom through tons of real-world experience. You will pick things up along the way.

Don't watch those tutorials with non-native English speakers or those with a bad accent as well. Native speakers explain things really well and deliver the message with clarity because they do what they do best: It's their language.

Trust me, I got caught up in this inefficient style a handful of times. Don't waste your time.

Update on my previous kernel rant, I finally compiled it down to just 2.9GB! included all the needed modules and I am also able to boot off of it!

Great news is, that sound both on speakers and also through headphones work, bad news is, that there's some overlayed buzz/distortion, the playback is higher pitched and chrome for some reason plays videos "normally" if you set it to 0.5 speed, else the video get sped up in the "normal" speed setting, well fuck me, but atleast I am closer, also as always thanks to arch wiki, that has tons of resources.

It might be some of the quick hacks that causes this, that I used in the past to make sound work through an external usb card atleast, so might be worth it just reinstalling it all.

Some of these things are not like the others. One of these people is a tv scientist not an actual data engineer or data scientist, while another is an activist and while is extremely respected, has no room in a data+ai talk -.-

Github 101 (many of these things pertain to other places, but Github is what I'll focus on)

- Even the best still get their shit closed - PRs, issues, whatever. It's a part of the process; learn from it and move on.

- Not every maintainer is nice. Not every maintainer wants X feature. Not every maintainer will give you the time of day. You will never change this, so don't take it personally.

- Asking questions is okay. The trackers aren't just for bug reports/feature requests/PRs. Some maintainers will point you toward StackOverflow but that's usually code for "I don't have time to help you", not "you did something wrong".

- If you open an issue (or ask a question) and it receives a response and then it's closed, don't be upset - that's just how that works. An open issue means something actionable can still happen. If your question has been answered or issue has been resolved, the issue being closed helps maintainers keep things un-cluttered. It's not a middle finger to the face.

- Further, on especially noisy or popular repositories, locking the issue might happen when it's closed. Again, while it might feel like it, it's not a middle finger. It just prevents certain types of wrongdoing from the less... courteous or common-sense-having users.

- Never assume anything about who you're talking to, ever. Even recently, I made this mistake when correcting someone about calling what I thought was "powerpc" just "power". I told them "hey, it's called powerpc by the way" and they (kindly) let me know it's "power" and why, and also that they're on the Power team. Needless to say, they had the authority in that situation. Some people aren't as nice, but the best way to avoid heated discussion is....

- ... don't assume malice. Often I've come across what I perceived to be a rude or pushy comment. Sometimes, it feels as though the person is demanding something. As a native English speaker, I naturally tried to read between the lines as English speakers love to tuck away hidden meanings and emotions into finely crafted sentences. However, in many cases, it turns out that the other person didn't speak English well enough at all and that the easiest and most accurate way for them to convey something was bluntly and directly in English (since, of course, that's the easiest way). Cultures differ, priorities differ, patience tolerances differ. We're all people after all - so don't assume someone is being mean or is trying to start a fight. Insinuating such might actually make things worse.

- Please, PLEASE, search issues first before you open a new one. Explaining why one of my packages will not be re-written as an ESM module is almost muscle memory at this point.

- If you put in the effort, so will I (as a maintainer). Oftentimes, when you're opening an issue on a repository, the owner hasn't looked at the code in a while. If you give them a lot of hints as to how to solve a problem or answer your question, you're going to make them super, duper happy. Provide stack traces, reproduction cases, links to the source code - even open a PR if you can. I can respond to issues and approve PRs from anywhere, but can't always investigate an issue on a computer as readily. This is especially true when filing bugs - if you don't help me solve it, it simply won't be solved.

- [warning: controversial] Emojis dillute your content. It's not often I see it, but sometimes I see someone use emojis every few words to "accent" the word before it. It's annoying, counterproductive, and makes you look like an idiot. It also makes me want to help you way less.

- Github's code search is awful. If you're really looking for something, clone (--depth=1) the repository into /tmp or something and [rip]grep it yourself. Believe me, it will save you time looking for things that clearly exist but don't show up in the search results (or is buried behind an ocean of test files).

- Thanking a maintainer goes a very long way in making connections, especially when you're interacting somewhat heavily with a repository. It almost never happens and having talked with several very famous OSSers about this in the past it really makes our week when it happens. If you ever feel as though you're being noisy or anxious about interacting with a repository, remember that ending your comment with a quick "btw thanks for a cool repo, it's really helpful" always sets things off on a Good Note.

- If you open an issue or a PR, don't close it if it doesn't receive attention. It's really annoying, causes ambiguity in licensing, and doesn't solve anything. It also makes you look overdramatic. OSS is by and large supported by peoples' free time. Life gets in the way a LOT, especially right now, so it's not unusual for an issue (or even a PR) to go untouched for a few weeks, months, or (in some cases) a year or so. If it's urgent, fork :)

I'll leave it at that. I hear about a lot of people too anxious to contribute or interact on Github, but it really isn't so bad!

Add this to the list of bad design choices of Mac OS and Apple laptops:

When you connect thr charging cable, the laptop makes a sound from the speakers, even if you have Headphones plugged in... Why?...
Infact it makes a sound even if you have it muted. This is an m2 pro, they had plenty of time to figure this shit out

:^) Think different I guess

I HATE YOU STREAMING SERVICES! FUCK YOU!

Here's the setup:

I work in a rather small office, where we are like 7 people (including me). Now, there's one person in charge of putting music through speakers (obviously, not everyone enjoys the same kind of music)

Well, we have a hell of a small bandwidth (1.5MBPS tops), now, add to that that every single fucker here uses "Spotify" and it's streaming their music...

WHY!!!!

Good side: I have my earphones and ~30GB of my music on my phone, so it's not an issue for me, also, I'm kinda audiophile, so Spotify quality sucks.

Bad side: I can't even fucking load Google because those fuckers are eating the bandwidth.

Every day in our standup bullshit, we have a few of our offshore team join via Skype. It always fucks up somehow, bad connection, quiet volume or dropped connections, all of which are quite hilarious but today a new benchmark was set.
We (the humans physically there) all did our standup, then it was over to the offshore team.
A voice came out of the speakers which sounded like someone had applied an effect to a spoken mp3 which slowed it down to about 10% speed. It was deep AF and slow AF and I couldn't speak properly after it for approximately 40 minutes 😂
My eyes were all red and puffy from literally crying with laughter.
Best. Standup. Ever.