[–] 3 points 2 weeks ago (2 children)

Sure, reddit might be a lost cause, but the data there was posted by people like us. As long as we import the content so to speak into lemmy instead of acting as a launchpad for reddit, I'm open to it. I would prefer we people who link to content on reddit do a write up around it similar to bestofredditorupdates sub though.

  • source
  • parent
  • context
  • [–] 22 points 2 weeks ago (1 child)

    I'm not mad that he likes ai; I'm a lead engineer, and I use spec driven development a lot. The problem is that I have had a career beyond ai and can survive losing ai, where as a lot of young developers these days can't. It's like that line from the Spider-Man movie, "if you're nothing without the suit, then you don't deserve the suit". He needs to talk about using ai as a tool without losing your skills and identity as a developer.

  • source
  •  

    The keyboard stops working after a while of inactivity like watching a movie or playing a game. The keys light up, and the 2.4ghz indicator on the keyboard shows it's connected, but my pc doesn't detect any keystrokes. Only after I unplug and plug the dongle again, does it start working. How do I fix this? Is this an issue on the linux side, or should I return the keyboard and get a Keychron v6 max?

     

    cross-posted from: https://programming.dev/post/51247328

    I use speckit, and while I like the spec/clarify/plan/task/analyze/implement loop (although it can get a bit overwhelming at times), I don't like that I have to start with writing a spec and implement it to begin with. I am looking for a more of a design phase before the spec phase, where I can talk about the overall application architecture, and then start writing specs for implementing pieces of it.

    For instance, let's say I want to build a github repo provisioner that 1. creates repos with desired setup, and 2. bulk edit repos with secret updates, yaml updates, etc. I don't want to build both the features at the beginning. I want to first build only the create portion, and then do the bulk edit feature later on. With speckit, I can do this by only telling it to create the spec for the build portion, but later if I want to build the bulk edit portion, the whole application might need to be changed in important places, because it wasn't a 'planned' feature when it was first designed. I want instead to have a design phase where I describe and maintain a doc with the whole application, and when I start the spec for the create portion, the agent can understand that this create portion is only part of a bigger application and can design/implement the create portion accordingly.

    Have you come across a situation like this? how do you handle your big applications? Please advise.

    view more: next ›