I was asking about LED lamps a few days ago. A few people linked to “Kōnā Floor Lamp” by “Noxu Design”.
DO NOY BUY THOSE. Noxu Design is a scam company. I bought their shitty lamp and that’s what led me to asking in the first place!
Here’s a small thread about how they operate.
Noxu Design is one of those companies that come up if you search for “LED lamp” or “corner lamp”. If you visit their website and don’t look closely, it might even look legit. But there are red flags everywhere! Can you spot them?
Red flag number one: they claim to be “award-winning” but there’s no mention of what award they refer to.
“Noxu by Norita Xudia.”
Who the fuck is Norita Xudia? Perhaps, a designer? No, it’s a fake person with 10 google results. This lamp must be their life’s work!
I think how people deal with this feeling is one of the most noticeable differences between experienced engineers and those who are new to the field. It’s something you can get much, much better at.
I thought I need to become “smarter” to get out of this. Turns out, it’s not primarily that but:
- Noticing when your mind can’t hold the whole picture, and using tools (pen and pencil)
- Learning good debugging strategies
- Grouping code to create guarantees I can rely on
Even the smartest people in the field aren’t some kind of cognitive monsters. We all have similar brains with similar limitations. But experienced developers are better at slicing the program in a way that each piece can fit in a human brain, while other pieces stat predictable.
Despite all its warts, MDX is a gamechanger for writing documentation and technical content. It removes the friction between the desire to add a bit of interactivity, and actually doing it in a way that surpasses your original intent. I can’t imagine going back to plain Markdown.
When writing, I used to “think in” Headings, Images, and Text. But now I can also “think in” in <FunFact>s, <Gotcha>s, <CodeSandbox>es, <Quiz>es and whatever domain-specific thing makes sense for this piece of content. Removing friction frees the imagination.
Unlike with a traditional CMS-backed writing, I don’t need a vendor to tell me what kind of blocks I’m allowed to use. I want to make my own in a few minutes.
My biggest problem with MDX is complexity of the stack. Hoping Server Components can simplify it in the long term.
What is this, you may ask? You see, a library compiled with webpack uses code splitting. But webpack doesn't know the URL at which my app is served. So it has some code that guesses the URL based on <script> src. Alas, its guess is wrong. So I fool webpack by giving a fake src.
Am I amazed? Yes. Am I horrified? Yes. Am I shipping? Oh yes.
Is there a good resource with questions that people get asked in real front-end interviews across the industry? Meaning 20-40 minute programming exercises. Can you send me the ones that you got asked, if you have them? Preferably vanilla JS, no framework stuff.
To clarify I’m not looking for actually good questions. I’m looking for what realistically gets asked today if you want to land a front-end job.
Let me make this even simpler. If you remember a question you really got asked (or know someone who was asked) for a front-end role.. and you have a link to it.. please send it in the replies! Thx