I gather from your explanation, that in order to tell before hand whether or not a type will be inferred, you really need to examine the code and see how things are being handled, and optimized out. (And even then you still may not know) Interesting, thanks.
wtf, lol that must be some damn good butta!
and very soon Facebook as well...
Ah, good point. I do have a monitor with HDR, but I never really paid attention to it in the past. AFAIK unfortunately there isn't really any good support for HDR without a lot of messing with the window server. It seems to be in the works though by various groups.
Great read, thanks!
Exactly, this just in... Water is wet
I really enjoyed this one as well, but I got super frustrated with some parts and ended up putting it down.
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.