Post

Lisp

i’ll say macbooks, did not take them seriously with those low specs the used to have, but god they are good for programming

TypeScript 😬 remembered bad memories about Java at first, now I couldn't code without it!

Oh yeah, Prettier is so nice here.

Yes. I absolutely hate finding one in the return block for JSX especially when it just gets added to and they negatives.

I've come to this realization as well recently 😅 is this true ? then this : is this true instead ? then this other thing : is this other thing true ? then this last thing Once you start reading it like sentences it makes a lot of sense

You could probably just search for question marks in your code and come up with some heuristic for whether they're nested in an expression or not depending on the language.

I agree. My brain can only process up to 4.

😄

until we get switch expressions it's the best we've got

THIS!!

No way, give me an IIFE any day!

For loops

for…of in preference to Array methods: easily read, supports await, loops over anything iterable, performant. I guess the corollary is learning to really embrace mutation: glad the fixation with immutability we went through as an industry a while back has simmered down!

Vim

TypeScript

TypeScript, Tailwind, and React. I'm still not 100% sold on Tailwind, but I like it much more now than I did initially. TypeScript has become an absolute must for me, and it turns out my scepticism toward React had more to do with lack of experience than anything else. 🤷🏼

This happened to me with promises and later with React 😄

Completely agree! But I’m biased.

Setting strict to true in a tsconfig

Vim, used to hate it now I like it - not my daily driver but feeling more comfortable these days

using JavaScript on backend (api) and frontend

I like having a mix of everything, depending on the "scope" of things. PascalCase for files, Enum and Classes, snake_case for things like hard-coded values and table names, kebab-case for CSS classes, and camelCase for variables.

I’d say low-level & typed programming languages. Sure, in the beginning it’s nice to have a neat python code, but with that I started to see some flaws within these kinds of implementations. It might be a preference thing, sure, but now I just love to see my explicit types and memory management!

Object Oriented Programing. When I was learning it in the early [REDACTED Time Period 😂]'s, I hated it and struggled. It was all supposed to be obvious & logical. Fast forward to today, and I think I really like it thanks to my TS experience.

Test Driven Development. As a junior developer I found it slowed me down and made things harder. But then over time you get better at it and starts to speed you up because you spend less time refactoring code to make it testable and you get more things right the first time.

Strongly typed languages took some getting used to because python was my first language. Now, weakly typed languages feel like the lawless, wild west

I did a complete 180 on @tailwindcss.com

Coding with AI. I often use it to help me think through problems and understand new things. Being able to help out my team on the backend side with tech I don't know has been great. I can write the code in JS/TS with familiar concepts/tools and ask it to translate to Python with a Python lib

TypeScript

kebab-case-or-nothing

you will learn with time my child

It’s the greatest

I feel so dirty using snake case 😰

Vue won’t allow me :-(

Interesting… hooks is when I lost all interest!

@tailwindcss.com was the biggest swing reaction for me from a decent period of "This is dogshit! Why?" to a quick switch to "this is amazing!". 7ish years later and it's still my favourite technique for styling on web.

PascalCaseFileNames

@svelte.dev . I couldn't understand what my brother was going on about. I was happy in my react-land (stockholm syndrome maybe?). Now that I'm using it I can't stop yapping on about it

Object oriented programming. Yes, I’m that old.

Always using curly braces for conditional statements. No more one liners.

Angular

0% unit tested code.

LISP, Clojure, Elixir, Erlang.. I've always hated functional programming. People seem to like them though, so I'm probably wrong.

Simply doing a "for" loop instead of trying to be super smart with map + reduce + filter + reduce again + some obscure lodash thing + etc. Code gets much cleaner and efficient.

Duplicating code until it actually becomes a maintenance burden

Switch statements and for loops

Before that: Tailwind Typescript React

My most recent one would be AI tools like ChatGPT. Was v skeptical at first, but now I lean on them most as a programming buddy whenever I'm learning new syntax or am in unfamiliar frameworks or tools. They can answer stuff in no time that would have taken me ages to look up previously

#dotnet Minimal APIs.

React and Tailwind - rode the vanilla train for the longest. I still have access to jQuery on a couple of work sites (I never 'disliked' it) and it's nice too.

PHP

Ok controversial: go error handling.

Tailwind. I think of Tailwind as a DSL and I’m tired of learning DSLs. It’s one of the reasons I don’t enjoy template-based frameworks. But you learn it and the speed gain is worth it. Use it with something like Astro where you dip into CSS no problem, it’s real nice.

I've been using Fork for years, I never learned how to do it in the CLI! 😬

I use GitKraken to deal with merge conflicts, blame, and history, but use lazy git inside neovim for pedestrian stuff like creating commits and swapping branches

For me it was TypeScript. After 20 years of JS, I didn’t see the need. Now I’m all in on strict mode. 😂

Definitely AI tools. Cursor is pretty nice a majority of the time. I also bounce ideas off Claude, ChatGPT, etc all the time

Structuring my code by feature (modules/auth, modules/blog) with kebab-case file names, instead of splitting code into components, hooks, utilities, types, etc., folders.

Does vim count?

Writing unit tests, for sure. Each testing framework has its own learning curve, and why would I want to write the test twice? Now I don't feel as if I'm appropriate defined the spec of my code if I don't have unit tests around the crucial logical hubs of my application.

Remix. I was not sold when it came out, but the more I explore it the more I like it.

Error handling in Go

I hated javascript when I started. But now I can't get enough of it. May be it is years of javascript stockholm syndrome talking 😅

SSR and HTML over the wire, all those technologies of rendering of processing the view in the backend and just sending it to the browser.

I felt the same way at first about Tailwind CSS, but it kinda grew on me recently. I started with styled-components, which I loved for keeping styles organized. Then I tried CSS modules, but they got messy and hard to debug pretty quickly. Tailwind has been a breath of fresh air compared to that!

I was the same, avid tachyons fan, thought there wasn’t any point in switching. Now done a full 180 and gone all in.

Haha 😆

What convinced me on tailwind was the easy way of adding responsive styles. No more media queries for me.

I admit I had a very "this is a stupid idea" reaction the first time I saw JSX and Tailwind. I changed my mind when I forced myself to use them and realised that the productivity gains were massive... And both technologies are actually a pleasure to work with.

Normal for loops and if conditions beat most fancy abstraction functions for me.

Coming from Angular, it felt wrong to me at first how in react it is common to put styles, logic and layout into the same jsx/tsx file.

useEffect (just kidding, it's actually the opposite)

Not taking LLMs seriously until Mar 2023.

📌

It's the default in the lint rule. Any rule that unifies things is good. We used to have PascalCase for components (CardHeading.tsx) but camelCase for everything else (dateRange.ts). Even worse: CardHeading/index.tsx 🤪. Never know what to do. Now it's enforced.

We've been looking at following FSD (feature-sliced design) for our new projects, very tempted to do this for all files as well - easy consistency for everything

Neovim. I didn't get why one should use it over Vim at first but now I love it.

JSX

Styled Components

Build tool configurations. Setting up Webpack was out of fashion for the longest time. I recall some very popular web devs at a major FAANG company saying, "Avoid it if you can." Now that I work with them more regularly, I realize why they can be a pain, but also what they allow developers to do.

Still use spaces but I’ve learned to appreciate tabs for all the good reasons.

C#/.NET