• 2 Posts
  • 105 Comments
Joined 2 years ago
cake
Cake day: July 10th, 2023

help-circle



  • 0x01@lemmy.mltoTechnology@lemmy.worldWhy LLMs can't really build software
    link
    fedilink
    English
    arrow-up
    11
    arrow-down
    7
    ·
    1 month ago

    I use it extensively daily.

    It cannot step through code right now, so true debugging is not something you use it for. Most of the time the llm will take the junior engineer approach of “guess and check” unless you explicitly give it better guidance.

    My process is generally to start with unit tests and type definitions, then a large multipage prompt for every segment of the app the llm will be tasked with. Then I’ll make a snapshot of the code, give the tool access to the markdown prompt, and validate its work. When there are failures and the project has extensive unit tests it generally follows the same pattern of “I see that this failure should be added to the unit tests” which it does and then re-executes them during iterative development.

    If tests are not available or if it is not something directly accessible to the tool then it will generally rely on logs either directly generated or provided by the user.

    My role these days is to provide long well thought out prompts, verify the integrity of the code after every commit, and generally just kind of treat the llm as a reckless junior dev. Sometimes junior devs can surprise you, like yesterday I was very surprised by a one shot result: asking for a mobile rn app for taking my rambling voice recordings and summarize them into prompts, it was immediately remarkably successful and now I’ve been walking around mic’d up to generate prompts.


  • Paywall, so replying based on the headline:

    Blue collar jobs are not a holy grail of safety from ai or refuge for prior white collar workers who have been displaced.

    1. You can’t just suddenly become an expert in a physical job, electricians require trade school and apprenticeship, heck even the easiest jobs in the construction world, painting or hanging drywall, require expertise and a random qa engineer will be genuinely terrible at the job.
    2. The culture of blue collar work generally incredibly misogynistic and requires a very hardy insensitive personality for women especially. There’s this sort of cultural inertia that has seeped into many blue collar jobs that sees a lot of love for trump and hate for soft handed people (the irony is incredible)
    3. Supply and demand are not just principles of product sales, a sudden massive influx of blue collar workers will push down wages for everyone, an economy requires balance and adaptation, there is never a single golden answer
    4. some blue collar jobs are more likely to be replaced with ai than others, but pretending that all blue collar jobs are perfectly safe from the impending storm is an uninformed and irresponsible take. Are indoor painters of new builds safe for now? Yes. But you can feel quite comfortable assuming that if some company comes out with a bot you can rent that does a phenomenal job at painting and costs 1/5th of a human painter the owners or managers of the companies who were contracting out the humans will absolutely switch to bots. Money talks and maybe some will hold out for a while but eventually other companies will offer their services for cheaper because of the cheaper labor and the human workforces will be unable to compete.
    5. blue collar jobs generally pay less and the future prospects compared to white collar jobs are significantly different. You don’t start out as a framer and end up as a partner, the attitudes of the managers of construction companies and similar often simply view the laborers as replaceable machines.
    6. blue collar workers sucks, for many you work in crazy harsh weather conditions (outside in 100 degree f) the jobs often require heavy physical labor, your coworkers are often drugged up conspiracy theory nutjobs, there are no watercooler breaks at 10am, you work hard or you get yelled at or fired. Imagine being an hvac repair technician in the peak of summer. Where exactly do you think you’re going to be? In the hottest part of the house in stifling conditions with all the pink fiberglass insulation without any ppe, all goddamn day.






  • Ngl I love tailwind, I’ve been through so many different css paradigms

    • separate css files: why did we ever do this, if you’ve ever used kendo’s css stuff you’ll understand how unfathomable hundreds of thousands of lines of css with complex rules is. Identifying all the things that affect a single component is the work of dozens of minutes at minimum, sometimes hours, you have to understand every nook and cranny of the css spec.
    • inline styles: fine, but verbose and requires object spreading, harder to compose, theming is tough and requires discipline to be consistent in your theme conventions, almost impossible to also theme imported library components
    • module.css with imported classes: my go to outside of tailwind
    • scss: I actually really like scss but it exacerbates the complexity and mystery of css, great for small projects but terrible as projects bloat
    • bootstrap: basically just worse tailwind, providing only components and colors

    That’s all I can think of right now, but tailwind is my preferred way to style a new project, I love how easy theming and style consistency is