The cost of energy in the EU combined with 10% inflation (but not salary increase) has become crushing to the point offices and households shut off heating and use battery lamps and candles for light. Avg. Year total for energy is over 9000€ in Belgium! At this rate we will burn through our savings for basic utilities

Last week I conducted a FE React-JS tech interview (high-level, no coding challenge) with a potential new hire. He knew his stuff in React 16.8+ but I was baffled npm install was the only npm command he could name, he'd never heard about semver, never used SASS, and didn't have any Nodejs exp. I asked him to name a tough situation he encountered and solved in React, and he said "too many re-renders, so we used useMemo and useCallback" but that's kind of basic and it was evident he didn't understand this meant passing props by reference under the hood. So I wrote a very mixed report, but this is only the 3rd interview conducted. Was I too harsh? To me this signaled a lack of curiosity (especially for a self-taught programmer which he was). My manager was kind of disappointed about the guy following my report.

We've all been there before mastering git commit --amend, rebase, and squash

That's gotta hurt dawg: Emotion(a CSS-in-JS library)'s 2nd most active maintainer ditches own solution for SASS + CSS modules: https://dev.to/srmagura/...

Didn't feel right from the start. Everyone showing their true feelings for CSS-in-JS in the comment section.

Please tell me the next big thing will be going back to basics & not go to even more insane lenghts for marginal DX improvements.

The failure of the free market, triumph of common sense and a big middlefinger to Apple https://greekreporter.com/2022/06/...

So if the current trend in software engineering is over-engineering, then the next can only be under-or appropriate engineering? =/

Definitely hoping it will be less proprietary, less custom DSL´s and grassroots driven

‘Groundhogging refers to the idea that people are going for the same type of person over and over again, while expecting different results,’ they explain. ‘People pick out someone who fits their ideal type, date them, but end up feeling underwhelmed.'
From: https://metro.co.uk/2022/02/...

Awfully resembles a pure function makeLoveHappenForMe with a single arg typeOfPerson:

const typeOfPerson = Jerk
// this is a pure function
makeLoveHappenForMe(new Jerk())
// will always fail
// but does it really have no side effects?

For some reason I always have a hard time mentally mapping "asc/desc" to dates. I think of stairs and mentally map the dates to unicode timestamps. Am I the only one? Sort descending by date is newest first, btw

git
Linux
VLC media player
Inkscape
LibreOffice
Metalsmith js

100's of low-level NPM packages I don't know the name of

RAAAAAAH fuck fuck fucking shit!!! Fuck jest Typescript "on the fly" compilation esModuleInterop typeroots, missing definitions jest ts-ignore and xtest everywhere, manual npm linking with different pkg mgrs & pub to a private registry, building docker images locally and doing tag management across git, docker & kubernetes then cross fingers that prod which has 0 common setup with local & test somehow works, open architecture "tickets" and wait months before they resolve, then repeat ad infinitum. How the fuck can I be productive when I need to be all over the place all the time and deal with these meta-code shenanigans. I just wanna code, damned

Should you not know or not have realised it years after your study: "video" literally means "I see" and "Volvo" (the Swedish car brand) means "I roll" in Latin.

This just happened when I randomly hit Inspect Element on a 250-item list. Must be a sign

In an object/dictionary/map config object where multiple source paths are mapped to destinations, which structure makes more sense to you (and why)?

1. { "src/path.ext": "dest/path.ext" }
2. { "dest/path.ext": "src/path.ext" }

Could also be a URI redirect map

Anyone else noticed this symbolism in the "compact" Google "G" logo?

The inner circle is like a walled garden of information with an open gate that is controlled by the G-atekeeper.

So watch out for the rebrand to Ooogle

Please share your thoughts on Dependabot security alerts on Github, more specifically for NPM packages in package-lock.json.

In 99% of cases I've found them useless as:
- package-lock.json is in the repo, but not in the NPM package (=no value to users)
- most of the updates relate to devDependencies (=no value to users)
- it clutters the git history (and changelog if it is auto-generated) with a batch of patch updates (updated depx to .1, .2, .3) while the only important thing in the next release notes is the delta (updated depx from .1 to .3) (=no value to users)

It powers nodejs.org. It has 7.8k stars on Github.
It was installed 5x as much on NPM in the last 4 months as it was in the previous 5 years. https://metalsmith.io

I've been doing a lot of outreach to individual users, websites, and related Github projects, yet community involvement is hard to get by. If you value copy-left or free open-source software and are interested in bloat-free nodejs static site generation or build pipelines, please reach out.

I have a full-time job and am thankful for any help, be it feedback on the Gitter chat: https://gitter.im/metalsmith/... maintaining one of the 15+ core plugins, creating starters or writing blog posts.

I quietly refactored an entire NodeJS express in-house framework that was written in Java style (dependency injection, inheritance, inversion of control) and split it into typed, composable, parameterized, testable middlewares in 2 weeks (including some complicated ones like a custom Openid Connect flow)

Now comes the hard part: convincing the Java-devs who wrote it that it is useful

"at least 3 alphabets"

Developing front-ends used to be about translating a business use case to an interface. Now I spend days and weeks getting tooling to integrate properly: webpack, babel, React, Vue, SSR, Nuxt, NPM packages, build & CI pipelines, storybooks, and resolving incompatibilities. It's become such a grind I haven't had a single satisfying, productive workday since 4 months.

Pseudo-flexible working hours suck. I get the "choice" to start work between 7:30-9:30 AM. I'm a night owl so waking up at 6AM is not an option. Why can't they just allow to start at 10AM and finish at 6:30PM? Between 7:30 & 9:30 is peak rush hour and I'm bound to lose 1h30 in traffic for 30km (normally it would take half an hour) and start my workday pissed off.

Pps with Nuxt experience, please help: Nuxt has a config option "ssr" that can be set to false: https://nuxtjs.org/docs/...

My question is: what is the point of using Nuxt if you set ssr to false, considering that I would use a lighter solution for static sites, or just Vue for an SPA?

In most businesses, self-proclaimed full-stack teams are usually more back-end leaning as historically the need to use JS more extensively has imposed itself on back-end-only teams (that used to handle some basic HTML/CSS/JS/bootstrap on the side). This is something I witnessed over the years in 4 projects.

Back-end developers looking for a good JS framework will inevitably land on the triad of Vue, React and Angular, elegant solutions for SPA's. These frameworks are way more permissive than traditional back-end MVC frameworks (Dotnet core, Symfony, Spring boot), meaning it is easy to get something that looks like it's working even when it is not "right" (=idiomatic, unit-testable, maintainable).

They then use components as if they were simple HTML elements injecting the initial state via attributes (props), skip event handling and immediately add state store libraries (Vuex, Redux). They aren't aware that updating a single prop in an object with 1000 keys passed as prop will be nefarious for rendering performance. They also read something about SSR and immediately add Next.js or Nuxt.js, a custom Node express.js proxy and npm install a ton of "ecosystem" modules like webpack loaders that will become abandonware in a year.

After 6 months you get: 3 basic forms with a few fields, regressions, 2MB of JS, missing basic a11y, unmaintainable translation files & business logic scattered across components, an "outdated" stack that logs 20 deprecation notices on npm install, a component library that is hard to unit-test, validate and update, completely vendor-& version locked in and hundreds of thousands of wasted dollars.

I empathize with the back-end devs: JS frameworks should not brand themselves as "simple" or "one-size-fits-all" solutions. They should not treat their audience as if it were fully aware and able to use concepts of composition, immutability, and custom "hooks" paired with the quirks of JS, and especially WHEN they are a good fit.

"I'm not distracted, I'm just very focused on something else"

Excuses that sound legit pt.2
PS: guilty

"I don't shy away from complexity, I avoid it when possible"

Excuses that sound legit pt. 1
PS: guilty

Anyone know of a good non-opinionated ESlint default config that does a little more than eslint:recommended? I find eslint-config-airbnb-base & eslint-config-standard to be way too annoying and restrictive

Really, Sass? Poor judgment for a styling tool

Typora was the best (closed-source) free markdown editor. As soon as it hit the first stable release, it became non-free. Luckily, you can still download the last beta from https://typora.io/releases/all (click Dev/Beta releases -> scroll down to 'More Beta')

So until now the default env var User directory paths for Windows were all located under %userProfile%. To my surprise:

cd %userProfile%\Desktop

no longer works. Indeed, when you are even just signed in to OneDrive (which is the default, even if you disabled backups!), these retards decided it was a good idea to move all the standard library folders one level up to %userProfile%\OneDrive\ instead.

And the worst is that the locations continue to be swapped when you enable/ disable OneDrive.. WTF Microsoft

1. Open private browsing window
2. Navigate to https://github.com

That's a really well-designed and inspiring product landing page.

Follow-up to my exp with Travis CI: https://devrant.com/rants/5006826

As my allotted credits are set to expire on December 23, I sent a request for 25k monthly OSS credits to Travis support on December 18.
Mind you this is only half of the credits of their lowest subscription price and I didn't ask for extra CPU, so not much to ask.

While for the previous credit request, I got an answer within 24h, this request has gone unanswered for over 2 working days and I noticed it got labeled with "Priority: low" although I will be unable to continue my OSS work in 2 days.

Let's see whether they plan to really uphold their promise that "they will always support open-source"