📎 links:

  • 1 Post
  • 11 Comments
Joined 1 year ago
cake
Cake day: July 25th, 2023

help-circle

  • All caps is a material design thing. ACCOUNTS is a button in this case, not a title. I’m assuming (although my knowledge is limited because I just downloaded the app) that this is intentional as material design is kind of the default Android look.

    The same style is applied other places such as the “CANCEL” or “EDIT” buttons displayed here, so it isn’t just one place.

    To be clear, I don’t know if they are following material design to a tee, but I do believe they might be taking inspiration.


  • Well, if I remember my software engineering prof correctly, software engineering is mostly about bringing an engineering mindset to software development. You wouldn’t just slapdash an airplane together in a weekend and shove it out on the runway. There’s a process for making sure we don’t kill people with deadly flying contraptions.

    Software engineering is that same idea applied to software systems. There is a process for making sure we do our job without causing undo harm. You wouldn’t want to just slapdash together something that has to be HIPAA compliant and has to meet other security regulations. You plan. You test. You revise. You ensure the product doesn’t publish the sensitive medical records of every patient on the front page before it ends up in production. That is the work of a software engineer.





  • Okay, so to be honest, at first, I didn’t understand all the ❌negativity, but I shared this with a friend to get her take on the issue, and she 🕵️‍♀️clued me into the fact that webpack already does this with copilot and pull requests, and the results . . . speak for themselves.

    Wow😅. I didn’t think it would be that bad. It seems that every example I find is just incorrect. I’ll look at the code. It will be a two line change, but the summary will be difficult to follow and often says things that are not part of the code changes. Then, there are also contradictions which make the pull requests harder to follow than if you just read the code with no other context. Darn it. I really thought this was a 🧊cool idea.

    I’m definitely going to be sticking to writing my own commits as always.




  • IMHO, the provided link is largely irrelevant to this topic. It is about lawyers who used ChatGPT as a search engine https://youtu.be/oqSYljRYDEM?t=1436, which is not what it is for, and it will tell you that over and over again. The lawyers in question were not even “trusting ChatGPT”. They blatantly and actively disregarded ChatGPT telling them that it was not a search engine and could not provide legal advice https://youtu.be/oqSYljRYDEM?t=1466

    This topic is about using LLMs to generate natural language describing code changes that it is provided with which is not only completely different than using an LLM as a defacto search engine, but it is also something LLMs are actually meant to do: autocomplete. This topic is more akin to using LLMs to write title headings for legal documents which are already basically complete as is than it is akin to the link provided.


  • Isn’t PICO-8 an IDE? I guess it doesn’t really fit the traditional defitinion, but it includes a code editor, image editor, and music editor.

    I would argue that PICO-8 is an IDE for game development on a fictional console, but I could understand why others would disagree. It is not necessarily what you would think of when you think of an IDE, but it is a development environment specially integrated with tools for game development. You can make an entire game without leaving PICO-8, and that sounds like an IDE to me.


  • What you are describing loosely sounds like the islands archetecture that Astro uses (however I have no idea if it lets you mix angular versions; that sounds cursed)

    Astro is a meta-framework like Next.js. Unlike Next.js, however, you could do exactly what you are describing. You can use both React and Angular (and even Vue and Svelte) components all in the same meta-framework.

    Additionally, you opt-in to all and any client-side interactivity. If you have components that don’t do anything after the page loads, you don’t have to client side render them.

    With that all being said, this might be totally unhelpful to you, but this is just what reading your post made me think of. I wish you luck in your breaking down of a large angular frontend.