@ThePrimeagen This makes me think of a comment i overheard at a recent conference. One engineer said to another "I was going to do some work during downtime, but with no Internet, I don't have access to AI, so I can't get anything done anyway."
@ashutoshrana_20 Communicate. It's up to you to give realistic expectations when you commit to anything. Tell your seniors & your direct mgr your struggles & ask them to help you make a plan. Don't overcommit & account for learning in your estimates. If they don't accept this, better to leave.
@AFCU can you at least explain why you are pushing out a new digital banking experience? Especially when it is so inferior to what was being provided previously (even with new features coming, you've inspired no confidence that they will be as good).
@AFCU@jonathantew Why would you release something that doesn't actually have all of the features you advertised? So many of us depend on these features and to just release something without them erodes trust in the competence of afcu as well as whether you actually care about members.
@AFCU The new update is absolutely terrible. Why would you ever release something that removes all of the features that made the app so good? On top of that, I feel like you tried to gaslight us all into thinking that this would be/is an improvement. This kind of move desolves trust.
@wesbos This happened to me with my kiddos... Twice. On the upside, you can get really good at Mario cart even though people use the squid ink on you (if you're 2nd or 4th player)
@allenholub ...paths that often duplicate logic needlessly. I think it important to strike a balance, but overall, my exp has been that creating a more client agnostic API leads to a more simple app & easier code to maintain & use overall. Granted you only add to it when necessary suggested.
@allenholub While I agree that it is better to have essentially full stack engineers working on vertical slices. My experience has been that your assertion that "unnecessary complexity is never introduced" is usually incorrect. Making an overly specific API tends to lead to many code...
Happy Father's day dads!
I'm at the end of raising my kids and my only regret is that we should have had a dozen of them
This video (not mine) describes my feelings perfectly
@kentcdodds Indeed! Fast prototyping, quick experimentation, shortening feedback loops, throw it mostly away and then applying the learnings... This is how AI will speed us up most apart from fast learning.
@djsmith42 I think it makes sense that we start with the things that most of us generally don't like doing, like working docs. I personally don't trust any of it enough to let it write code unsupervised. You make a great point about having it do other things though, we are missing out.
@shcallaway As I've recently been experimenting with trying to run many agents in parallel, I've learned first hand how very true this is. It's exhausting switching between everything and I don't trust another agent to manage it for me
@thdxr I have this run while I'm working on work that matters way more and check in periodically throughout the day to give it some guidance. I review when it's done and then find another piece of cleanup i need it to do.
@thdxr This is one of the primary things I've been using Claude for lately. Our semi large codebase has gone through a few phases with little attention to updating the existing code with each new phase. I'm quite specific about what I want and do a little at a time, but it's working.
I just ran an AI coding course for ~2,000 people
One massive piece of feedback was how dissatisfied people are with frameworks like BMAD, GSD, Spec-Kit
Turns out that giving away control of context to a framework makes things a lot harder to debug
My advice: own the process