Post

So good! I had the same revelation!

All of the top browsers come with powerful developer tools built in. Tools that will show you raw requests and responses, analyze and tinker with CSS in real time, set breakpoints so you can inspect JS variables. Learning how to use these tools is a real power move.

This is all amazing! Thank you :-)

I don't know where I'm going with this, but I guess my "seniority" is just having some clue over the sausage and how ugly it is. And still being able to see beauty in it as well... Maybe? :D

i’m building otelic.com and would love to make it accessible, i wonder how alternatives work for people using screen readers, could i provide better

Flash! Imma gonna wash your mouth with soap!!! 🤣

1999

Nothing showed this better than a spacer.gif at 100% width.

Spring Framework

Something a dear co-worker said to me frequently: “We can always refactor later.” Sounds trivial, but it really unlocked a mindset that plays into agile/scrum as well as TDD, if you think about it. We can always find a solution, then iterate it, make it better.

All your input so far has been amazing! Thank you so much!

a) It can be a good idea to add more stuff than the client/design asked for – not only small animations but also semantics, accessibility, performance etc. And b) I have more fun with web dev when I can add small details – even when I am the only one who knows about or appreciates them.

I was a designer, a colleague lent me a book for the weekend - chapter 1 was conditionals, chapter 2 was for loops. That was 2001 and I haven't really needed anything else.

There are dozens of small aha moments. How HTML maps to the DOM, how simple HTTP (1.0) is, that browsers read CSS selectors from right to left, how setTimeout, events, promises, generics etc. work, but also the importance of good UX.

And another one: break down what you're really doing into basic terms. Often technical terms make things sound more complicated than they actually are. Example: an Auth guard is really just an if statement.

training none-techy people how to use software. it was such an opener about a decade ago. since then i look at ux with different eyes :)

A big one is breaking big problems down into a lot of smaller problems. It also took me a long time to get confidence in my ability as a dev, but over time as I accomplished more projects and worked with people earlier in their journey, I came to realize I do have the skill and I’m pretty good!

Same. Great one

This was mine, too!

Another might be while learning OOP, asking myself *why* they were generically called "classes" and "objects". The former much like CSS classes, because the instances share qualities. The latter because an object is tangible, able to be used and handled, unlike the class which only describes

The browser is a wonderful platform to build for xkcd.com/1367 To answer your question: Realizing the end boss in web development is not how to center a div, but the fact that the pipe between us and our users will always be limited. This is why we need to be smart about what we send over and how.

Simple is good

It was the click of imposter syndrome dying that made me a senior. Just recognizing that I know the details of the tools and can find solutions more effectively than when I started.

tbh i can't remember having an aha moment but what i considered useful on my journey to becoming a web developer is having a good understanding of the basics first (mdn is your friend) before jumping into frameworks, design systems, bundlers, alternative runtimes. a strong foundation is key.