3 ms·
No in my case the “how” is 1. I spoke to sales to find out about the customer 2. I read every line of the contract (SOW) 3. I did the initial requirements ga
by raw_anon_1111 8mo ago
No in my case the “how” is
1. I spoke to sales to find out about the customer
2. I read every line of the contract (SOW)
3. I did the initial requirements gathering over a couple of days with the client - or maybe up to 3 weeks
3. I designed every single bit of AWS architecture and code
4. I did the design review with the client
5. I led the customer acceptance testing
> We as an industry have been able to offload a lot of “how” via deterministic systems built by humans with expert understanding. LLMs
I assure you the mid level developers or god forbid foreign contractors were not “experts” with 30 years of coding experience and at the time 8 years of pre LLM AWS experience. It’s been well over a decade - ironically before LLMs - that my responsibility was only for code I wrote with my own two hands
- deleted 8mo ago[deleted]
- ansibsha 8mo agoYes, and trusting an LLM here is not a good idea. You know it will make important mistakes. I’m not saying trusting cheap devs is a good idea either. I do think cheap devs are actually at risk here.
- raw_anon_1111 8mo agoI am not “trusting” either - I’m validating that they meet the functional and non functional requirements just like with an LLM. I have never blindly trusted any developer when my neck was the one on the line in front of my CTO/director or customer. I didn’t blindly trust the Salesforce consultants either. I also didn’t verify every line of oSql (not a typo) they wrote.
- icedchai 8mo agoActually, it's SOQL. I did Salesforce crap for many years.