Most kids just want to code. So they see "Computer Science" and think "How to be a hacker in 6 weeks". Then they face some super simple algebra and freak out, eventually flunking out with the excuse that "uni only presents overtly theoretical shit nobody ever uses in real life".

They could hardly be more wrong, of course. Ignore calculus and complexity theory and you will max out on efficiency soon enough. Skip operating systems, compilers and language theory and you can only ever aspire to be a script kiddie.
You can't become a "data scientist" without statistics. And you can never grow to be even a mediocre one without solid basic research and physics training.

Hack, I've optimized literal millions of dollars out of cloud expenses by choosing the best processors for my stack, and weeks later got myself schooled (on devRant, of all places!) over my ignorance of their inner workings. And I have a MSc degree. Learning never stops.

So, to improve CS experience in uni? Tear down students expectations, and boil out the "I just wanna code!" kiddies to boot camps. Some of them will be back to learn the science. The rest will peak at age 33.

I was watching "hacker reviews hacking scenes from movies", and god forbid they brought a woman to do the analysis. A lot of butt hurt boys in the comments, that women left the kitchen and got into programming.
This aside, the combination of ignorance and arrogance was just wow. I mean, if you want to be a dick, at least back it up with skills.
Don't make claims about how "GUI is the single most important piece of any software". *laughing in embedded programming*

developer: *deploying spaghetti code to production*
hacker: *alters the code with an injection*
developer:

At the institute I did my PhD everyone had to take some role apart from research to keep the infrastructure running. My part was admin for the Linux workstations and supporting the admin of the calculation cluster we had (about 11 machines with 8 cores each... hot shit at the time).

At some point the university had some euros of budget left that had to be spent so the institute decided to buy a shiny new NAS system for the cluster.

I wasn't really involved with the stuff, I was just the replacement admin so everything was handled by the main admin.

A few months on and the cluster starts behaving ... weird. Huge CPU loads, lots of network traffic. No one really knows what's going on. At some point I discover a process on one of the compute nodes that apparently receives commands from an IRC server in the UK... OK code red, we've been hacked.

First thing we needed to find out was how they had broken in, so we looked at the logs of the compute nodes. There was nothing obvious, but the fact that each compute node had its own public IP address and was reachable from all over the world certainly didn't help.
A few hours of poking around not really knowing what I'm looking for, I resort to a TCPDUMP to find whether there is any actor on the network that I might have overlooked. And indeed I found an IP adress that I couldn't match with any of the machines.

Long story short: It was the new NAS box. Our main admin didn't care about the new box, because it was set up by an external company. The guy from the external company didn't care, because he thought he was working on a compute cluster that is sealed off behind some uber-restrictive firewall.

So our shiny new NAS system, filled to the brink with confidential research data, (and also as it turns out a lot of login credentials) was sitting there with its quaint little default config and a DHCP-assigned public IP adress, waiting for the next best rookie hacker to try U:admin/P:admin to take it over.

Looking back this could have gotten a lot worse and we were extremely lucky that these guys either didn't know what they had there or didn't care.

I remember I was a child trying to tinker around the only computer that we had. No one knew how to install the Windows OS from scratch with the drivers and everything else (they were installed on floppy disks) so when no one was around I managed to do it everything. I remember such joy, felt like a hacker 😂

Now I'm a web developer and I feel like a moron each time I'm sitting on a defect I can't solve so I'd say these were good times 😜

i have been applying for jobs recently, and after getting some HR interviews that evolved to tech interviews, i just cancelled them all...

Every company seems to have hacker rank, and online coding sessions as tech interview stages which really stress me out. Its like everyone thinks they are google and its ok to make people go theough this pressure to join them.

I dont mind being given 10 days to implement a complex project, after which im either in or not. But 20 mins to solve something online while either the interviewer is watching me or the automated test is waiting to filter my application out... i get anxiety just thinking about that..

so im gonna stick with my current job for now, and focus on building my own business slowly on the side. I really felt anxious because of those tech interviews these past weeks and i feel so much better after cancelling all of them.

if a decent company comes along with the project approach, id love to apply, but otherwise ill just stick to where I am for now. dont know if im being immature or irresponsible career wise or if this decision will blow up in my face

stay tune to find out !

How many years experience as a dev do you need to feel like the cool hacker guy in the movies instead of a blind monkey trying to play the violin for the first time?

Goals for 2022:

- Keep studying my new book (concrete mathematics)
- keep solving hacker rank problems
- Interview at amazon.com again (I was so close to get it) and feel the pleasure of reject them
- Stop skipping gym days
- Making friends in NY

How can i be a hacker from begging to pro?

Who's dream is to become an ethical hacker and who else ? 💻🖥️