Bri'ish Python devs be like "noice wever today, __init__ ?"

I don’t like to judge people based on what languages they like (because I like all of them). But I can’t deny the pattern anymore.

Smart people know and enjoy smart languages: Smalltalk, OCaml, Clojure, Lisp, Haskell, etc. They may use JavaScript or PHP to make money, but ask them to code in their smart language and they’ll be more efficient. Getting old, some of those people say “screw it” and find a Haskell job.

You, my friend, are not one of those people. You are VSCode-dwelling goblin who thinks lambda calculus has something to do with JS arrow function notation, is scared of reduce() and not even good at the single fucking language they know.

Insta coders and that mechanical keyboard collector dorks are not “superstars” you got to be like.

My young brother just destroyed everyone at a speedcubing competition!

4x4, 3x3 one handed, 3x3 regular (the main event), skewb, pyraminix — all 1st places!

!rant

I love ruby????? I just started learning it so far It's so good!

Ec2 mac instances🤔

True shit...

For some reason, Tableau is really heavy. I mean, all reporting software is a little bullshit, but Tableau... The server we had took 45 minutes to restart (no exaggerating - we timed it).

Reading the log files, yes, it WAS doing shit the whole time. Lots of shit. It seemed to be running just... Tons of software.

Tableau seemed to be aware of this because they have a page where you can check the status of everything. I assume that starts up first.

If you're looking into Tableau, two things to consider:

1) No, your braindead financial manager won't be making their own visualizations, no matter how many times the marketing team writes "drag and drop" on the Tableau website.

2) You'll make some nice visualizations but find that when you try to do more complex things, you run into constant roadblocks. If your manager asks "can you make it do x"? No matter how much experience you have, your answer can never be 100% "yes"... Or even "no" for that matter.

Not the worst experience with enterprise software, but definitely a surprisingly bad experience.

I think we've skipped the telepatic one...

ref: https://newscientist.com/article/...

I have a love hate relationships with Google.

As an investor, I love how they are a natural monopoly that keeps growing into new areas...

As a deaf user, And I hate how they find ways to screw me over while still looking good.

When companies don't understand what DevOps is and don't know how to implement it.

I hate when the term DevOps gets slapped onto a traditional Ops or sys admin team and they call it a day.

It's become the new agile.

Sorry Facebook recruiters, I don't think I can work for a company that has all the information that would likely prevent me from getting a job in the first place.

I think a question should be added to tech interviews and maybe the most important one.

How many times in a week do you use Google/internet to look for a solution to/information about ur problems.

Tests for a developers ability to learn or try to figure things out themselves..

Feels like a lot of people on my team just do it the way it's always been done ,. Which is ahitty.. and if they don't know something,.. they need to ask someone instead of trying to figure it out themselves...

Reminds me of that fish adage?

They never learn how to fish....

Is it too much to expect an integrated Terminal or launch terminal from Xcode?

Arrggggg...

I login this morning

Everyone going crazy as prod is broken in a million ways. 2.5 million exceptions In 24 hours.

We talk for 1 hour and solve nothing.

I diagnose the 2 biggest sources of exceptions and explain every step I took with screen snippets to reach my conclusions

The one other competent person on my team agrees. Otherwise complete silence.

I'm told not to fix the issue because I am leaving in 6 weeks and other people have to start taking responsibility.

No one fixes the issues. Instead they leave early. Now it's the weekend and the product is fucked.

Fucking useless people. Can't wait to leave.

Who else has never seen Stackoverflow's homepage?
😂

Don’t work here.

Put away the keyboard. Think about what you're going to do, chart it out, work through the logic and then, when the entire construct is before you, you start typing.

Yes it will take longer, you're a junior, enjoy that nobody expects you to do miracles (yet) and take the time, you'll get it back when you're so used to working through logical problems that it happens on its own as soon as you hear about the problem.

Cutting corners and "hacking a quick solution" without fucking over the entire system is an art form. Before you do art learn your damn craft.

Someone is whining about how hard Git is in an article they wrote. They work for GitHub. The article was posted to HN.

Yes, let's make things so easy a literal baby can do it.

Juniors are a fun bunch to work with.
Over confident, hero complex of that fresh graduate high, and then thrown in to the real world! Where there hopes and dreams are crushed in minutes when they see what monolithic applications really look like!!

But don't let that overwhelm you, your not going to be changing all of it any time soon, hell some of this code hasn't been touched in 5+ years and still works without fail.

Don't stress about the work load, you can only write 1 line of code at a time anyway, and hell, even seniors make mistakes.

The key about being able to manage this beast is simple, break it! Because the more you break it, the more you'll understand how a project is put together, for better or worse. Learn from the examples in front of you, and learn what not to do in the future 😎

But more importantly, plan your changes, whiteboard the high level logic of what it is you want to add, then whiteboard in the current codebase and determine where to slice this bitch up, then when it all looks well and good, take out your scalpel and slice and dice time.
Don't worry, your changes aren't going to production anytime soon, hell, you'll be lucky to get past the first pull request with this working 100% the first time, and that's a good thing, learn from tour short comings and improve your own knowledge for the next time!

1. You don't code to add a feature or whatever. You do it to solve Users' problems. It's a User-centric system.
2. You read more code than you write. So help yourself and write code intended to be read.
3. If people don't know you did something, you did nothing!
4. Never answer a call at 3 am if you're not paid to be on night call-duty. You'll become the guy who answers at 3 am.
5. Remember the big difference between you and me is that I failed to do stuff more times than you have tried to do.
6. When you start shaving the yak, stop!

Not my original, but cheers to the creator since it's hella relatable!

That's ***VERY*** nice, @Root

Did i just get rick rolled through a user agent?

"[17/Nov/2020:10:20:42 +0000] "GET / HTTP/1.1" 200 1274 "-" "We are no strangers to love. You know the rules and so do I. A full commitment is what Im thinking of. You wouldnt get this from any other guy.." "-""

This post made my day...

FUCK VISUAL STUDIO ANBD EVERYTHING IT FUCKING STANDS FOR. PIECE OF SHIT IDE CANT HANDLE MORE THAN THREE FUCKING WINDOWS AT A FUCKING TIME WHY CANT A BILLION DOLLAR MOTHERFUCKING COMPANY MAKE COMPETENT SOFTWARE FOR ONCE? WHY IS MICROSOFT SO FUCKING AWFUL IN EVERYTHING IT DOES? WHY THE FUCK IS THERE NO AUTOMATIC VERSIONING LIKE EVERY CIVILIZED BASIC FUCKING IDE THAT EVER EXISTS? WHY DO I HAVE TO FUCKING MANUALLY VERSION MY FUCKING FILES? WHY THE FUCKING FUCK IS VISUAL STUDIO FUCKING GOING TO A FILE I USED 300 YEARS AGO WHEN I DEBUG AN APPLICATION? MOST USELESS, UNINTUITIVE PIECE OF SHIT SOFTWARE IVE EVER USED. IF YOU ARENT USING SOME GODDAMN SERVER SOLUTION TO KEEP TRACK WITH YOUR PROJECT VERSIONS, GOOD EVER FUCKING LUCK RECOVERING LOST CODE BECAUSE FUCKING MICROSOFT CANT DO WHAT FUCKING INTELLIJ DID 5 MILLION FUCKING YEARS AGO

Programming tutorials on pornhub

Can't remember how many times I had to change project structure just because they provided wrong/misleading/half-ass requirement

Fuck you Android Studio. FUCK YOUU...

How do you like my new two monitor setup?

Read the error message before closing it and/or asking for help.