#thoughts

If you are a fan of console.log, you must be using turbo console log.

All you need is to set it up in 1 min for the right shortcut / linter and enjoy it.

One feature I particularly enjoy is deleting all console logs with just one shortcut 🔥

https://marketplace.visualstudio.com/items?itemName=ChakrounAnas.turbo-console-log

#thoughts

So state of JS results are out for anyone who haven't seen them:

https://2021.stateofjs.com/en-US/libraries/front-end-frameworks

If you get asked what to learn when starting or which tool/framework is better, I find it useful to point the person to this kind of results. And they can decide what they want eg learn smth new and cool, get a job, play around etc.

React is quite stable in its high scores over usage (can't say the same on satisfaction).

"Vite" looks like it can be the next big thing at this point, but we'll see.

PS also that link has mentions of what people usually read in dev space, who they follow and what podcasts listen to (which is always great to explore 😉)

PPS Their data visualisation is pretty sick 🔥

#thoughts

And just to make it easier for the lasier ones here. Those are the people to follow ☝️

How many names do you recognise?

#thoughts

This one looks like an interesting thing to try

https://intab.io/

Not like browser devtools are much worse, but who knows until you give it a go.

So far looks like code editor with export features and nice UI already win.

#thoughts

Alright, if you are using vscode auto close tag and bracket pair colorizer extensions, delete it now. They slow vscode down.

Go to vscode settings (command + P on Mac, type >, and type "settings") and search for "colorize" -> and enable bracket pair colorization

Then search for "linked editing" and enable that as well.

The first thing colorizes multiple } brackets that really help and the second renames the matching open/closing html tags automatically.

Super useful if you still don't use them. And much more efficient than similar extensions.

PS All this cool stuff you found being integrated in your IDE when you attempt to speed it up. Amazing 🔥

#thoughts

If someone ever ask you to define the word "beauty", send them this

+80 Readibility Points by default

#sarcasm

#thoughts

It's amazing to see such well defined and properly thought design systems and UI elements

I'd give their designer a payrise right now 🔥

#sarcasm

PS oh yes ladies and gentlemen, welcome our new hashtag. Next ones on the list are #joke whenever I try to be funny and #image whenever I post a pic

#thoughts

Entry level full stack job descriptions be like 🤷‍♂️

#uiux #thoughts

I find it entertaining how Apple is trying to push a thought that Safari is modern and all with its latest "oh, look at mac OS Ventura and Safari 16! How cool. It can support Web Push notifications🔥"

Even better - Web Push on iOS and iPadOS in 2023!

Meanwhile Chrome supported push notifications at least from 2015.

All of this aligns quite well with what a dev for web telegram pointed out in 10+ things while Apple is slowing the industry with its Safari.

Side note: the webK/webZ telegram client is actually sleek. I use it myself.

Side note 2: if you just want to read a bit more on Web Push notifications, explained and compared to app ones this link is for you.

#news #thoughts

Just look at this.

I mean we got rid of IE (in fact, it's gonna die in about 20 hours from you reading this).

And Safari is either gonna end up in the same boat eventually or Apple gets pushed by regulators and finally support the industry.

#thoughts

I know people hate redux for adding too much boilerplate and generally being applicable to medium/large projects.

And of course mobx or even recoil are a bit nicer (my subjective opinion).

But what's the hype with zustand? Looks good, but any of you actually tried it on large projects?

https://github.com/pmndrs/zustand

#thoughts

Ever experienced something like that?

#uiux #thoughts

This is the exact part I've tried to avoid in rich text editor. Somehow it always felt way too cluttered to me.

I know that's kind of a standard (probably reinforced by Microsoft back in 90s), but c'mon - this has to go away eventually.

#thoughts

We vs I

I see a lot of small channels on telegram using typical corporate invention and say "We" anytime they share something.

"Today we prepared for you.."
"We were quite busy lately"
"We found this cool tool.."

You get the idea.

It's totally understandable to have that in some work environments (especially where teamwork is valued more than individual achievements).

But when it comes to your personal projects, blogs, channels, personal websites etc not only I find it weird, but also damaging.

People do that to create a mental protection and share responsibility if something goes wrong (eg they've made a mistake or were completely wrong in what they shared).

Also it makes it sound like the statement is more valid (which is just a bandwagon fallacy).

The only problem is that if you are on your own there is noone to share that responsibility with, pretending that you have a team of 20 people behind you is useless as this would just bump up expectations that you ll likely won't meet.

There is absolutely nothing wrong in saying "I" like in examples above, especially if you doing something on your own. In fact, despite corporate bullshit it makes things more personal, cosy and simple, helping to set the right expectations with the crowd.

Rule of thumb unless you are in corporate ecosystem.

Was it just you involved in it?
Yes - use "I"
No - use "We"

Keep things simple in a not so simple world 🫡

#thoughts

www.layoffs.fyi - someone created a trackable, filterable layoff tracker since Covid 19.

Maybe can be an interesting find when you thinking which companies to send your resumes to.

#tools #thoughts

Aand yet another no-code-build-native-apps-fast-enough service, but this time somehow it feels more thoughtful than others.

https://flutterflow.io/

So ios/android + out of the box firebase support for your backend seems neat. Anyone tried it? Any feedback?

I generally smile at those, but that one kinda made me think "OK, if I need some quick prototyping or basic MVP might give it a go". Surely you still gonna need to learn it as any other tool really but that one looks like a week top.

#thoughts

Big mistake #11 - Using React 😂

Source (which is actually a link to a free webinar if you are bored)

#thoughts

Speaking of QR codes.
Image above is a totally valid QR code. Had a bit of playing with stable diffusion over the weekend.

Might take a bit to get recognised by a scanner, but that's the balance it's tricky to keep (recognisability vs making it non-obvious).

This AI stuff is hyped for a reason guys 🔥

#thoughts

Today I had a pleasure (not really) getting to think about how far should I go in supporting Safari.

At some point I found this which basically quoted:

Safari is the baseline in terms of web standards: The sites we develop must work in Safari versions at least 2 years old.

Which somehow resulted in aiming at Safari 13.1.2 with ended support in 2020 but some users still on it.

Boy, did I suffer. I'm using Antd as UI lib at work and let me just mention 1 thing - Grid is broken everywhere on our latest version.

One thing you'd hope UI lib does really well is grid and layout, I can add border-radius to buttons myself..

How is that possible that there is a browser out there that is still so bad?

Speaking of which, I'm currently using Arc for my main browser for more than 2 months and couldn't be happier with it (if any of you folks looking for a switch)