I cringed when I saw a dev literally copy and paste an AI's response to a concern. The concern was one that had layers and implications to it, but instead of getting an answer as to why it was done a certain way and to allay any potential issues, that dev got a two paragraph lecture on how something worked on the surface of it, wrapped in em dashes and joviality.
A good dev would've read deeper into the concern and maybe noticed potential flaws, and if he had his own doubts about what the concern was about, would have asked for more clarification. Not just feed a concern into AI and fling it back. Like please, in this day and age of AI, have the benefit of the doubt that someone with a concern would have checked with AI himself if he had any doubts of his own concern...
I did a similar thing with a car design for Mercedes-Benz when I was around the same age. I had all the car drawing books and really thought I was going to be a car designer. Much to my surprise, they responded with enthusiasm and even sent me a Mercedes-Benz keychain :)
Having lived in Japan it feels they either they go all in on minimalist or maximalist. Some stores are quiet, others are obnoxiously loud and brightly lit to where you don't see your own shadow. Some magazines have a ridiculous amount of text on the cover, distorting the characters to fit with bold text stroking, others especially fashion might have one line if any at all alongside their logo. Game and book covers can be more on artistic/subtle side whereas in the west we often fight for your attention with character collages or action scenes.
We basically tried wrapping an entire registration app into the Shadow DOM just for a hopeful kick but it came with weird accessibility quirks, arrow keys not always working to go through selections, and some overlays acting strangely. We were using Shadcn which is powered by Radix Primitives, however, and a setup they probably weren't expecting or testing their code to be in.
But for smaller things like chat widgets or players I think it's a great solution.
I didn't have a problem until I migrated to another Mac. Then I started having duplicate files. I think I fixed it by logging out of everything and deleting the duplicates but it was a couple hours wasted. Didn't have this problem with Dropbox in my career.
Thanks, I was wondering how in the hell that many would get the answer wrong and what is this hidden equal sign he was talking about.
Maybe the question could be flipped on its head to filter further with "50% of applicants get this question wrong -- why?" to where someone more inquisitive like you might inspect it, but that's probably more of a frontend question.
I don't think LLM's are that great at manipulating SVG unless you mean like small edits like rotation and font size. Cool article though, I'll have to think how I can leverage it.
Yep. I'll admit I've acted faster to hard set dates than some "in the future" message. I've also seen some tools become really noisy about deprecation spanning many lines AND repeating. Please don't log the same message over and over for each instance. Color or add emoji if you must to grab attention, but once is enough. It's annoying when you can't do anything about it at that time and have to sift through this extra noise when hunting down another issue in the CI log. Add a link that goes over it in more detail and how to migrate for that specific deprecation.
Use <table> for tabular data, but for layout you should use grid. Grid doesn't have it's own element like table does, so you have to use css to apply that display to a div.
CSS takes a bit of time to understand. It's cascading nature and how certain properties behave differently based on the html structure or display type or direction makes it tricky. I don't blame you sticking with tables for layouts for yourself - making layouts with floats was a pain. Bootstrap hid a lot of the layout pain. But today we have flex and grid to help us realize our layouts.
Yeah, to expand on that... Flex is, well, flexible, whereas Grid is more rigid like a table. The rigidity of Grid allows you to span rows and columns (2D) just like you can with table cells (colspan/rowspan). Grid is usually used at a macro level for its more deterministic layout (no unintuitive flex quirks), while flex is usually used to lay things out at a component level where you don't care that the next row of items isn't perfectly aligned with the ones above (you will often see it hold some buttons or badges, or vertically align text to an icon), and Grid setting the layout of the app and container components (modals, cards, etc).
I agree, it's improving by leaps. I'm still patiently awaiting for my niche use of creating new icons though, one that can match the existing curvature, weight, spacing, and balance. It seems AI is struggling in the overlap of visuals <-> code, or perhaps there's less business incentive to train on that front. I know the pelican on bicycle svg is getting better, but still really rough looking and hard to modify with prompt versus just spending some time upfront to do it yourself in an editor.
Yup. I think a lot of the devs that started with React jumped straight into the "fun" stuff without learning some of the "boring" fundamentals.
And those devs set the wrong patterns and standards for others following hot behind them. The only time I can remember needing to dress a div up like a button was when an accordion trigger was just a giant button and anything passed in would be rendered inside, but I needed an action to the right of the trigger title. But those happen super rarely. You can't just pass in a button as it was invalid html to have nested buttons obviously. Yes, I know I could probably use css to absolutely position it or something but that takes it out of the flow and starts hacking about it in another way.
Yep, it just works seamlessly. Sure, it hangs sometimes, but their UI allows you to retry or undo changes to an earlier point in the conversation easily. The autocompletion is nice as well and pretty satisfying to tab through the small and menial things when refactoring.
True, but it's for my forgetful self where I raised the volume on the mac speakers to play something aloud, then plug in my earphones and play some death metal only to get up and walk away quickly accidentally yanking it out. At least 10 years ago it would continue playing the music at whatever volume I had the mac speakers on.
I wonder if the phone has an auto volume off feature after no sound plays after n minutes? I have an app on my mac called AutoMute that does similar, but it just mutes my mac whenever my headphones get disconnected.
JS is the logical place to start with all the virtualization and fanciness.
But CSS has bit me with heavy pages (causing a few seconds of lag that even devtools debugging/logging didn't point towards). We know wildcard selectors can impact performance, but in my case there were many open ended selectors like `:not(.what) .ever` where the `:not()` not being attached to anything made it act like a wildcard with conditions. Using `:has()` will do the same with additional overhead. Safari was the worst at handling large pages and these types of selectors and I noticed more sluggishness 2-3 years ago.
I liked the UI of BitBucket more. Stuff I accessed frequently like commits and branches were tabs across the top, easy to reach from any page. Branch dropdown sort order was by most recently updated unlike GitHub where I have to search for it. Easy to diff files. This was like 4 or 5 years ago though, maybe it has gone through modernization/enshittification. GitHub feels a bit fragmented and it tries to be more performant by virtualizing some things but while BitBucket in some sense was more rudimentary and showed it all (bogging my machine down some), it allowed me to CTRL + F easily with more confidence whereas with virtualization I've had issues with it finding things and I couldn't 100% trust it.
It also can't seem to create icons from another set and match the stroke weight, curvature, and other stylistic choices of another simple icon set. Seems it struggles with tight constraints. 10 years ago you would think it would be able to handle the visually "simple" things over the more complex ones it can do today. Sorry, my disappointment is showing isn't it?