Monkey Island 3 (the true 3rd in the series) will be released in 3 hours.

Old schoolers like me are unusually excited.

https://mixnmojo.com/countdown/

Don't just blindly do what's asked to be done by superiors. Be critical, suggest alternatives and take ownership of and participate in processes beyond your own scope.

Best decision: becoming self-employed.

Worst decision: not doing it 5 years earlier.

.NET

!rant

Just completed Monkey Island 1 and 2 again, 30+ years after I last played them.

1. What an awesome blast from the past
2. I am getting old.......
3. Can't wait for Monkey Island 3 (the real third)

If refactoring scares you, fuck off out my team.

If you keep code in the codebase simply because it took you ages to write it, fuck off out of my team.

Some people must be wishing pain and suffering upon themselves and their colleagues.

// todo: refactor this!

Advice from me to my future self.

I am looking at replacing my Dell XPS 15 from 2019, but because I work 100% remote I am considering building a desktop developer rig instead of getting a new laptop. I have only had laptops since early 2000s, but thought it would be fun building something from scratch again. The problem is I have fallen tragically behind on everything hardware, and therefore looking for some pointers.

I don't want an RGB rainbow unit with 6 loud fans requiring a noise cancelling headset to work on. I want a top spec, stealthy thing that has all the goodies but also runs quiet. A decent graphics card that can run the latest games at a decent frame rate, but not the top of the line either.

Any tips on cases, motherboards, RAM, drives, fans and grahpics cards appreciated. The budget is roomy, comparable to a top spec Dell XPS 15 or ThinkPad X1 Extreme.

Take the leap and become a self-employed contractor years earlier.

All right, I am not one to criticize people based on their looks but I will make an exception. Mark Zuckerberg er one weird and extremely untrustworthy looking human.

Maybe it's preconception, maybe not.

Read 1/5 of the requirements and then fire up VS and start coding.

What's the longest lifetime of one of your applications where you did a significant portion of the implementation?

I just got a warning message out of the blue from one of mine. It was written in 2005/2006 several employers ago and still going strong!

Stopping myself from always proclaiming how things "should have been done in the first place" - as if I never implemented anything the wrong way.

Too much focus on hinsight is an ugly thing.

Just realized that CRON only supports up to year 2099.

Y3K might become what Y2K was hyped up to be. Time is ticking...

23 comments on a single PR.

Am I a nazi or a good tutor? I think so.

Oh my fucking god.

How can you, after 2 decades as a developer, still produce code to this very day that has that many warnings and suggestions that Visual Studio lights up like a bloody pinball machine from all the squiggly lines!?!

Take your craft seriously or find something else to do!

Does anyone have a good suggestion to a (PC) game that is quick to fire up, runs in a window and offers some distraction for 5-10 minutes at a time while I wait for docker builds to complete, deployments to finish etc? Just braindead shit, like Clash of Clans on mobile for instance.

Can't decide whether I like React or not. Hated it in the beginning, then sort of started liking it and even thinking it was great just to fall back to the dislike stage again where I roll my eyes and think it's a messy, crowded pile of shit that breaks with all sorts of good software principles. This has fluctuated up and down for over 3 years.

It's the only language/technology/framework I have had this experience with. Weird.

Finally fashion makes sense to me.

When will managers understand that there is a huge difference between a UX designer and a graphical designer?!

FML. The time wasted trying to explain that the proposed GUI is rubbish because they put a graphical designer in charge of planning the entire application flow..

Always try to work with people more skilled than me.

Sharepoint. 'Nuff said.

Donald Trump reminds me of the type of code I wrote back at my very first job as a developer.

It was built wrong from the ground up, required way too much resources and space, contained flaws and bugs in almost every method, spat out random and inconceivable messages in the log and threatened to blow up at any given time. But for reasons unknown it kept going, managed to fool people it wasn't as shit as it really was and the client couldn't get rid of it even if they tried.

Don't be a dev if it's just not for you.

It's not for everyone, and you should figure this out at the very early stages of your education. The ones it's not for that still persist will hate their life. And leave their job. And leave unfinished, crappy code behind for the rest of us to clean up.

Becaue you are getting paid really well to build what is essentially virtual LEGO!

Streams in Java. What a joke! That was the answer to LINQ? Come on....

Can anyone with some AWS IAM skills please shine a light on this one: I needed access to create a slack notification for a job in Code Pipeline. Simple enough, but we (devs) have next to no access to AWS so every time I try something I am stopped by the red "user X is not authorized to perform Y on resource Z.." warning message. I send an email to OPS and ask for permissions needed to do what I need (in this case: create a Slack notification for a pipeline), and I am granted that specific one. It gets me one step further, until I am stopped by a new red warning message. This has been going on for over a week, with a total of TEN new authorizations added to my user. That's TEN red warnings, TEN emails asking for access, and TEN replies saying "Ok, can you try now?". Today I finally got the god damn slack notifier set up, only to get one last red warning slapped in my face: I am not allowed to SEE the notifications configured for my pipeline. Please insert four letter word that rimes with DUCK here: [_________]!!.

I REFUSE to believe that this is how access should be granted in AWS. Can I tell my OPS person that there is somewhere they can find a list of required access rights to complete a specific operation ("Create slack notification for pipeline")? I know there are example policies for various things, but if there isn't one for what I need how should OPS go about granting me access without this totally ridiculous "try again now" approach?

Oh, and @assmaster: don't comment "nice" to this one. This is shitting me off.

Happy 25th birthday, Windows 95.

A guy that just did not know how to code. He had years and years of experience (?), but DID NOT KNOW HOW TO CODE. He was given a simple task, spent weeks on it and what came out was usually 60 lines of "if, elseif, elsif....else".

He was given several warnings, and eventually "voluntarily" left the company.

I still get screenshots of his code sent by one of my ex-colleagues who's still there when he stumbles across it.

Finally read the Steve Jobs autobiography.

That guy is going to make it big!