Happy-creepy coffee

I suck at DevOps at least as hard as I'm good at front-end/UX. I found out as a result of the local job market starting to get needy for 'full-stack'. Stuck for 2 days on setting up a Docker/ Dockerhub/ DigitalOcean/ Bitbucket pipeline with Nginx/ Node/ MongoDB Cloud & Webpack/ React.

*Sigh*

The night before I had an oral exam about history of Communication Studies at university, I was too excited about learning PHP (ikr, that was 5 years ago). I mailed the professor an apology and stated the real reason I would skip this exam. When I still showed up at 9 in the morning without having slept, he told me "that's the most honest mail I've ever had" and gave me a 2/20 for showing up. (At the third exam period I studied it properly and got an 18/20)

The search engine that understands programmers. Way to go, Duck Duck

Unpopular opinion: I actually enjoy writing HTML/CSS, the only frustration I have with the latter is lacking browser support

devRant, devRant, you're my devRant.
And, baby, you can turn me on - turn me on, darlin'!

Lorem ipsum dolor sit amet.
I studied Latin for 6 years in high school.
A dummy text is the link between my education and my job

°_°

My kick-ass merch from JapanCon Brussels (Nov 2018): a Yoda doormat, TallGeese Gundam Wing model, Pulp fiction displate, AND in front of it A 3D-PRINTED PICKLE RICK OMG CAN YOU BELIEVE THAT!!! xD

Imagine in the future a sponsored tweet "Dear followers, I am no longer among you. This message was posted by my heirs, who accepted the terms and conditions of my will, which included letting my followers know in case I'd no longer be here. Get yours too with Buffer (https://buffer.com/)".

That would be the pinnacle of capitalism

Apparently the standard "pack" of applicants for a job is at least 100 people, how else can you only be in the top "2%"? If there's only 2 applicants, your fingers (typing skills?) are in the top 2%, and the rest is in the upper 48.

All of that just to say it would have been better worded as 2 in 100 people than 2% =).

https://grammarly.com/blog/...

Damn, Natasha Bedingfield's Unwritten accurately describes the start of my workday coding sessions.

One day in a near but comfortably not too near future, I will start a webdevelopment 3-letter-abbreviation dictionary page, with self-taken photos of Belgian car license plates, and use the alphabetic part for each definition. It's insane how many PSD's, JSX's, PHP's and other technologies and file formats I've seen driving around and can no longer keep it for myself.
To qualify the tech/ format must 1) have been spotted and photographed by me and, 2) be about something related to webdev

If it doesn't take off, I can still create a unique custom CAPTCHA service with the photos :D

How do devs React when they realize Vue is upside-down triAngular? (Share ur clever answers)

Isn't it curious that most development libraries, frameworks, widgets in an ecosystem see a decrease in popularity when they reach a "no longer under active development"/ maintenance stage (especially exacerbated in the front-end)?

As if we just can't settle on a convention. As if, even for limited-scope solutions, a final stage can never be reached, there must be perpetual growth. As if we must constantly trade a solution for a shinier one, that just might provide us with 2% profit based on a doubtful forecast... or not. Sounds a lot like the investment capitalism that resulted in the 2008 subprime crisis. Not sure what to make of this thought but

FUUUUUUUUUUUUUUUUUUUUUU

The amount of repetition and vagueness in this unsollicited recruiter job invite is insane: "Current Technology Sector Consultant". I've had 10's of invites from these recruiters on Linkedin, blocked all of them and they just keep coming back despite my Linkedin preference being set to let recruiters know "that I'm NOT open to opportunities"

If you ever get an offer from VMR consultants / J People consider these reviews carefully: https://glassdoor.co.uk/Reviews/....

I'm naming the company because it seriously deserves to be exposed for its bad practices towards both their potential and current employees.

Make navigation menu great again

I feel connected in all the word's meanings. To give you some context: I'm high, it's illegal, but at least it's outside of office hours

Enjoy this ultra⁻DRY piece of React-JSX-Redux-form component

That moment when you read a Redux article titled "The Perils of Using a Common Redux Anti-Pattern" as part of educating yourself on the stack of the app you're paid to continue development on, go back to the code of the application, and realize the ENTIRE REDUX STATE WAS BUILT ON THAT ANTI-PATTERN. I thought I was the Redux noob!! #FML

URL: https://itnext.io/the-perils-of-usi...

The best Redux logger is the simplest (in-browser: console.log(store.getState())

Fuck the ScrumTime app

Estimates.. First, part of the team makes "high-level" estimates which are based on informal, incomplete, still-evolving specs and an unstable back-end. The project people report the estimates to the client and elevate the status of these inaccurate estimates to that of commitments.

Then, before the "sprint", we review our initial estimates *ahum commitments* in greater (technical) detail. Because there are still a lot of unknowns, we tend to estimate more buffer here (back-end is often not ready, always ping-pong between project people and dev-team about unclear specs, more work than originally expected, and often late modifications to the original spec).

When an estimate becomes more than 50% extra time at the "refinement", we are told: "sorry, we gotta do it in less" and when it doesn't work out, we're kindly asked to spend part of our weekend catching up at 100% pay rate (legally it's 150-200%).

FUCK THIS SHIT

*quotes used abundantly because these terms belong to "agile/scrum" terminology but we're only pretending

create-react-app is HUUUGEE (in a literal way)

Yes you are. Not a single reason. Clearly no one. I am very surprised. This recruiter put in some very subtle irony and lots of effort (google "minutes in an hour")

Fuck you! I'm really starting to like this npm package, https://npmjs.com/package/fuck-you/

I see a lot of React devs (ab)using the array.map function in cases where a forEach would be more suitable (e.g. without assigning the result, and without return statements). What are your thoughts on this?

When you join a React JS SPA project months after the start to discover that 2 CSS grid systems with totally different breakpoints have been in use in parallel since 5 months, hidden by layer upon layer of abstraction, and that no dev bothered to fix, let alone notice.
#FML