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

help-circle


  • Good:

    1. I have high hopes that Nepal’s new government will bring positive change
    2. Crispr science combined with some new good results with protein models may help us develop some incredible new health technology
    3. In the financial world, less reliance on the US, and a shift away from usd in general would be a huge boon to the international community

    Bad:

    1. Massive economic instability worldwide, inflation everywhere, people will have an even worse time affording things once the worlds petrol distribution eases up
    2. taiwan’s troubles are likely to pick up the pace with more international events to smokescreen their bully to the west
    3. The transition to ai will likely push more of our society to crime, and lower the payment bar for many professions





  • 0x01@lemmy.mltoTechnology@lemmy.worldWhy LLMs can't really build software
    link
    fedilink
    English
    arrow-up
    11
    arrow-down
    7
    ·
    2 months 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.





  • 0x01@lemmy.mltolinuxmemes@lemmy.worldWhich git branch are you on?
    link
    fedilink
    arrow-up
    36
    arrow-down
    2
    ·
    3 months ago

    The default branch for some projects is “production” since CD deploys on pushing to that branch

    For new projects, main. My thought is that even if master is not offensive, since the industry has generally made the change, the only reason to stick with master is stubbornness or hating political correctness, neither of which aligns with my self-view so I’ll use main and move on.

    In general if people are genuinely hurt by the use of some words, I’m not sadistic so I’ll avoid using them. From my perspective morality is the pursuit of the reduction of suffering, even if that suffering is internal.





  • 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





  • We have one in an upstairs bedroom from midea, the window slides right between the front and back of the unit and it’s excellent. Our power consumption didn’t increase too terribly much and it’s actually decently quiet.

    Not gonna put the model here but just look for U shaped window units. It has little legs that go outside.

    Don’t get the inside standing units, they’re massive, loud, power hungry, and most of them are less effective than even the cheap window units.