Something like Stackoverflow is probably the biggest source of code to train a LLM on, and since it’s based around posting code that almost works but you got some problem with it, I’m absolutely not surprised that the LLMs would pick up the habit of making the same subtle small mistakes that humans make.
Holy shit, it actually works!
Ooh that looks good! Thank you so much, that definitely lessens my worry about iOS not cooperating at all haha
It’s beautiful and very handy, if you use it exactly like they want you to! Getting it to play nice with custom components is so fiddly though ;_;
Godspeed! I can’t even handle Tailwind yet since I’m so used to MaterialUI’s stupid styling system. Gotta break out of those proprietary systems and rawdog CSS one day, but today is not that day yet…
Oooh the latter would make so much more sense! I’m not a cloud developer, but a good chunk of the code I write runs in AWS Lambdas and EC2 Images and I was so confused as to what relation that would even have to local storage. If anything, I’m afraid of Terraform and it’s arcane power
Hey, this is awesome for saving space when writing things to NFC tags! Every bit still matters with those suckers
Side question, we all put Html, Css and JS as skills on our resume, right? How well do y’all actually know those? Would you be able to beat CSS Diner on the first try? How many different Html tags besides div have you actually used? Can you explain what an array reducer function does or how a Promise works?
I bookmarked another post from this community that might relate nicely!
It’s time for modern CSS to kill the SPA
Haven’t gotten to trying all the cool css stuff in my own projects yet, but it certainly sounds interesting :D
Had to google it, but those books do actually exist!! I am totally getting them as a decoration on my desk at work.
I started out as a React developer and have been radicalized when I wanted to optimize my hobby website to run on crappy mobile data. The thing sends 3MB of Javascript on every full page refresh. I am now learning jQuery.
Using AI to write Unit tests is one of the few use cases I somewhat understand, but even that turns out horrible with improper supervision. I reviewed one Pull Request once where the testing was so horribly cobbled together and nonsensical that I rewrote those tests by hand (after asking the person I was reviewing to fix it twice and them only making it worse by letting their AI rewrite them)
Bookmarking this, so far I’ve cobbled my Dark/Light Mode switch together with Material-UI themes, but this seems like the cleaner way to do this that I’ve been searching for!
I only figured this out like, a month ago! I only became a frontend dev when I got shifted into a new team at work, so I came in with zero prior knowledge and have been using exclusively React and Typescript since Day 1. Didn’t even know how to add a css class to something or what tags beside <div> html has until I started a personal project, ran into performance issues (while hosting it in a shitty aws free tier micro t2 lol) and started investigating why my code loads 3MB of Javascript every time I refresh the page.
I’m working on getting better at it in my personal project, might even try kicking React out entirely and seeing whether just Laravel Blade + Livewire already does everything I need. No way that I’m rocking the boat at work tho.
…i mean, I get it, I’ve written some very scuffed JS in my time because using .filter() right before displaying my data felt easier than getting the right data to begin with. Especially if the backend is in a different git repo and uses some whacky ORM library I’m not familiar with, while the Product Owner n e e d s everything deployed today.
But you can’t tell me that applying filter/sort to 8MB of data in the frontend is anything but mega scuffed. Imagine you need to debug that and don’t even have an intermediate step to see whether the wrong data is arriving or whether filter/sort logic is wrong for a specific case, or whether its just the rendering. You’d always need a person understanding all three just to debug that one part.
Not to even mention how that would run on low-power devices with bad internet connection. Or what that does to your SEO.
Huh, wouldn’t just plain sql be perfectly fine for that use case? Make a get request with your filter/sort params, server-cache the result, return the data with a client-cache header. I’ve been serving up customized svg files like that in a personal project of mine and its been so much faster and cleaner than styling my svgs within the jsx.
I don’t get the concept of “learning” a specific programming language, you can’t just sit down and learn the entire thing at once. You use it, google its weird quirks whenever you come across them and get better with it over time.
I’ve always been really language agnostic, which led to me being shifted into a Delphi team and then into a Typescript/React team. Didn’t know anything about those languages when I entered the team but someone who’s willing to just try their best can be a lot more desirable to a company than someone who thinks they can’t do something just because they didn’t spend time learning it “properly” first.
Also, might just be a regional thing, but the last time I went to one of those “I just finished university and want to network with companies” events, like 70% of the CS graduates were looking for Data Science positions. Seems like it’s quite the saturated market.
You have paid for Minecraft once, there is nothing immoral about pirating it now.
We were having pretty big problems with our yarn configurations a few weeks ago because the default npm registry is now blocked for security reasons and we’re supposed to only use our own internal registry. The coworker who was supposed to fix it asked his AI whether he can override the configuration for the location for the default registry and the AI said no, so he closed the ticket as “can’t do anything about it I guess 🤷”. A few days later, another coworker just went and changed that configuration by looking at how custom scopes are defined and using common sense. Worked instantly, we haven’t been having any yarn issues since.