Our prof told us today in a zoom lecture: "Never visit b-ok.org, it is totally illegal", with emphasis on how he would NEVER recommend to visit that website for free education illegally.

I guess he is totally against the idea of pirating educational material

The level of fucking backflips I have to do to get these morons to learn git and not share code via fucking emails, Jesus Christ, you'd think I asked them to switch religions. Why the fuck does this profession not require a fucking license in this godforsaken country.

My advice to those juniors working with their boss,

if u tried to get close to him/her for any reasons,

don't become friend with each other.

just don't ask why?😏

Sometimes, I run tests just because I want a break from writing code. In good cases it's so that I take a moment to think about what I'm going to do next. In most cases however, I'm struggling for motivation

can we make a dev confession/bad practices you do anyway chain in the form of o'reilly books in the comments?

https://dev.to/rly

here's mine:

I recently joined to a company. I am recent grad. I was getting KT by my Manager during team on-boarding.

The manager showed me the tech stack they use for the application. It had the given logo.

My manager read it like this - "We also use Adobe here ....."

I muted my mic and laughed so hard, and now I am searching for jobs at some better company- where managers don't confuse AngularJS logo with Adobe.

If you only have 30 laptop stickers and 20 funko pop dolls, are you even a real fullstack ninja/rockstar?

Abuse "new" google meet background feature level : 999

- while in meeting take screenshot of one of my team mates
- mirror the screenshot and put is a background
- now pretending that I'm at their place

after half an year of lockdown... It was fun

This female collegue whom I used to hangout during tea and lunch has suddenly started hanging out with another female collegue.

I'm alone, sad and overthinking is killing me. I asked her if there is something I said or did that made her hang out with someone else.

She said it's not a big deal and I should stop creating drama. I think I lost my self-respect while facing her about this.

Here's a real tip for people new to the industry.

It's one of those things that's been said over and over again but very few can really seem to employ. I suggest you learn it /well/.

You are not your code. Criticisms of your code, ideas, or your thought processes, is not a criticism of YOU. You absolutely cannot take criticisms of your work personally.

We are engineers. We strive to seek the best solution at all times.

If someone has found a problem with your code or with an idea or whatnot, it is coming from a place of "this is not the best solution", NOT "you're an idiot".

It's coming from a place of "I'm closing this PR because it is not a change I feel suits this project", NOT "I'm closing this PR because it's coming from a woman".

It's coming from a place of "This feature request is ridiculous/this bug is not actually a bug", NOT "you're a fucking idiot, fuck you".

It's coming from a place of "I've already had to address this in a number of issues before and it's eaten up a considerable amount of my time already", NOT "I don't even know you and this I don't have time for a nobody".

You do not get to be bitchy to maintainers because they denied your request. It's not a reflection of you at all. But if you're arguing with someone who has maintained a piece of code for almost a decade, and they're telling you something authoritative, believe them. They're probably smarter than you on this subject. They've probably thought about it more. They've probably seen their code used in many different places. They have more experience than you with that codebase in almost all cases.

Believe me, if we cared about who was behind all of the issues, pull requests, etc. we get, we'd get NOTHING done. Stop taking shit personally. It's a skill, not a defense mechanism. Nobody has the time to sugar coat every little thing.

Let's normalize directness and stop wasting time during technical discussions into opportunities for ego-stroking and circle-jerking and back-patting.

Compiled new linux kernel for my phone today.
All went good.

Except it got really hot and it appears that my sdcard died.

At least now I can tether over bluetooth.

Yesterday I had a phone screening with a hiring manager and was expected to talk about more of my expertise and just my experience overall. With four years of experience, I thought I could tell her everything she needed to know.

However, this interview was just kind of... weird. Literally every question she asked was defintiions. It was as if I was doing a short answer quiz.

"What is object-oriented programming?"
"What is a hashmap versus a list?"
"What is class inheritance?"

Like... What the fuck. These are questions that give no insight into who I am or how I work. This is shit you see on a second-year midterm exam. What a waste of time.

* KISS (keep it super simple)
* don’t try solve a problem you don’t already have
* admit if you messed up. We can solve a problem early and minimise the damage. People should never be scared to admit when they mess up. No one is perfect.
* voice your opinion. You’d be surprised how helpful this can be to your team, as we need to look at things from all angles.
* help your team. If you see something wrong, make the team aware of it.
* ask if unsure, don’t assume

Trump: I pay taxes as little as possible!
Me: I write code as little as possible!

I have written less than 2000 lines of code in production in 5 years(about 2 line per working day)but with my luck, I earn more than average wherever I live. God, I live this profession AND my luck.

Note: I write fewer sloc not because I am lazy but because of my industry.

Reinvent the wheel, then throw it away.
Best way to understand a concept

Just reported a minor tracking bug I found on WebKit to the WebKit bugzilla, and I have a few thoughts:

1. Apple product security can be kind of vague sometimes - they generally don't comment on bugs as they're fixing them, from the looks of it, and I'm not sure why that is policy.

2. Tracking bugs *are* security bugs in WebKit, which is quite neat in a way. What amazes me is how Firefox has had a way to detect private browsing for years that they are still working on addressing (indexedDB doesn't work in private browsing), and chrome occasionally has a thing or two that works, with Safari, Apple consistently plays whack-a-mole with these bugs - news sites that attempt to detect private browsing generally have a more difficult time with Safari/WebKit than with other browsers.

I guess a part of that could be bragging rights - since tracking bugs (and private browsing detection bugs, I think) count as security bugs, people like yours truly are more incentivised to report them to Apple because then you get to say "I found a security bug", and internal prioritisation is also higher for them.

Confession:

I rely on WolframAlpha to simplify Boolean logic a little too much.

I am new to coding.
Where can I do practice Web Development projects?

Generics look kinda cool. But it doesn't takes long before it becomes a giant mess. And then a manager asks for some new functionality and you end up changing every class that inherits from it. I hate and love it at the same time. A confusing relationship.