Related Posts
Hello All, In the next couple of months i am targeting companies like Apple , American express, Salesforce, Microsoft etc. Can anyone please share the required skill set and preparation strategy for these companies? YoE - 4 years Current skill set - Advanced SQL , Pyspark,Azure services, Hadoop ecosystem , shell scripting, Power BI
I am not very good at DSA.
Apple Microsoft Salesforce Amazon
Anyone want to go on a date today? 🤷🏻♀️
Additional Posts in Software Engineering
Rising Star
Anonymous User
Where/ how can I learn Azure?
New to Fishbowl?
Download the Fishbowl app to
unlock all discussions on Fishbowl.
unlock all discussions on Fishbowl.
With you re: junior devs. They need to build a solid foundation, then start experimenting with AI. Disagree if you're talking about experienced devs who already have that foundation.
Bowl Leader
You're not wrong.
Anytime we offload a "skill" to someone or something else long enough, that skill diminishes and eventually perishes.
Spell and grammar check and auto correct has had the same effect. Spelling and grammar were skills taught in school back in the day and you had to be good enough at it to graduate.
Technology has had this effect every time it evolves to over take what once was a human skill.
What we tend to not forsee are the transitive consequences (or the law of unintended consequences). Sure, development skills will suffer, but what is the next consequence after that? People start writing faster software and bringing garbage software to production en masse? What happens after that? The same thing every time garbage software hits the market as a trend. Think of when web designers learned PHP and started writing crap software? Graphic artists started writing their own solidity (literally painters writing financial software)? Mathematicians writing software for AI?
The market pushes back and the processes and protocols that create that software either are reverted (rarely) or mature enough that the deficiencies in the production are remediated and the software once again meets a minimum level of garbageness to be considered production quality. Until security teams come along. Then rinse and repeat.
The key is in the remediation of the process. The risk is having software "developers", let's call them software coordinators, who don't have the skill to understand why a AI developed may not be the best. Whether the AI used either a bad design patten, or inefficient one. You need skill for that.
So do we remediate by increasing software coordinator skill to elevate them to software developer? No. That takes a lot of time and hence money. Instead, we are going to increase the efficacy of our AI models as well as usage (we've seen this in adversarial agentic pipelines where agents work against each other until software isn't garbage anymore before it gets shot out the other end; akin to what rock tumblers do with stones and minerals).
Once we get this down pat, the next step will be in automating and digitizing everything since there really will be an app for absolutely everything. And if there isn't, you can make it while you sleep.
What does THAT world look like? What's the next step in software coordinator after that? We are relegated to testing the software that AI decides to write itself? Or does it spin up it's own version of QA after that?
This is an unstoppable train.
One of the questions people will eventually need to ask themselves is whether they are software developers because that is their profession or because that is their passion? If it's because a profession, then you need to learn to follow the value of the market.
Yeah, there are pros/cons to using AI to generate code. On the one hand, it's quick. On the other hand, it's not always correct, and sometimes it's just wrong.
The company I came from, just laid off earlier this month, is going all in on AI, but "keeping" a human touch. But almost every Staff or Senior Staff engineer is ambivalent about using it.
I also do not think companies are considering the long-term effects of AI usage either. If you don't support young engineers and help them grow, the talent pool will become stagnant.
Totally agree. It’s a force multiplier for people who already know what they’re doing. For people who don't, it’s just a faster way to head in the wrong direction. We’re essentially trading long-term foundational growth for short-term ticket velocity.
Chief
It’s a great post and I hope we coach our direct reports accordingly