Second on the Octopath Traveler II music. Even my son who is 9 and plays it as well as a ton of other games has only ever commented about how the music is really good on Octopath Traveler and no others (and I had never mentioned this to him). It's definitely the best music I have every heard for a game. There was a glitch one time where the music wasn't playing for some reason and I realized how much the music made the game come to life, NGL, I think it brings like 99% of the emotional engagement to it.
Early Gen X, late millennial here. This, wondering how we are going to pay for the skyrocketing health care, day to to living, and send our kids to school. We are told to invest in 401k's which after living through the dot com bust and housing crash, is a total fucking gamble. How are we going to live? I.have.no.fucking.idea. To be blunt, this country just doesn't give a fuck, I expect to be working until I die.
Exactly, this just in... Water is wet
According to Biden if you are black and you voted for Trump, nothing, because - “You got more questions, but I tell you what, if you have a problem figuring out whether you’re for me or Trump, then you ain’t black.”
lol, wow...😀
Agreed, this experiment should be able to last by itself without feeling obligated to post something. If that's the case then it's failed.
If the code is written well, it can save a bunch of time and provide a great forum for learning new techniques. Otherwise, if it's written poorly yes I hate it. Like others have state here the title is an over generalization.
I started out where everyone else did and worked my way up so I've "been in the trenches". After doing this for 20 years and shipping multiple consumer and internal products I've seen it all and know what can make or break a project and what works and doesn't when introducing or using a new technology to a dev group. Also, I definitely don't throw it over the fence, it's a team effort and we all agree on what sounds like the best approach. Along with code reviews, part of the coding I discussed is sitting down and creating a skeleton of tests and an initial architecture that others can build off of and give me feedback on. If someone is having trouble implementing something I sit down with them and work through it. It's also about trust, people also trust me and know that in general I know what I'm talking about. The thing is most people would read my resume (or even this quick summary) and say I'd make a great development manager. But the problem with being pigeon holed into being a manager just because your a great dev is that it doesn't reflect what developers are good at, making software. More and more companies are realizing this when they shove their best dev engineers into the position of a manger and it crushes their souls, and makes them leave. So they are creating these principal or staff positions which at most companies are laterally equivalent to a director of software engineering without the people/staff managment. There's a great podcast episode on this by Stephen Dubner who wrote the book Freakonomics https://freakonomics.com/podcast/why-are-there-so-many-bad-bosses/
This is really useful info, can you recommend a tutorial that you feel shows how to effectively use these tools along with traditional style coding? Or would you say it's just a try and see approach/learn as you go. Personally, I think your comment best demonstrates where we are right now with AI assisted development.
Great interview, thanks