4 ms·
> Some exec wakes up one day and has a crazy misguided idea about sticking gen AI somewhere and then asking junior (non DS) devs to build it without DS input D
by spacebanana7 3y ago
> Some exec wakes up one day and has a crazy misguided idea about sticking gen AI somewhere and then asking junior (non DS) devs to build it without DS input
Don't really see a problem here - it's quite realistic for junior devs to build something useful out of Ollama/Open AI APIs.
- fieldcny 3y agoI can’t tell if you are being sarcastic, or you are just inexperienced
- llamaLord 3y agoBy "useful" he means "will make VC's and uninformed investors feel good"... gotta remember, the definition of "useful" is relative.
- catchnear4321 3y agowhat’s most useful is how many heads can be removed above the junior level and below the exec level. that’s a lot of cash saved. basically as good as cash earned, when you’re getting funding rounds of cash.
- spacebanana7 3y ago"useful" means something that helps people. Realistic examples of small, useful AI projects a junior dev could do in a sprint: 1) check for spelling/grammar mistakes on company website 2) summarise transcripts of zoom calls 3) scan codebase for misleading comments 4) generate mermaid diagrams from terraform 5) Scan Jira for near-duplicates on a backlog and add a label None of these require data science teams to get involved.
- deleted 3y ago[deleted]
- jncfhnb 3y agoAs a data scientist, there’s basically 0 data science involved in building a small tool out of the api or high level model interfaces.
- deleted 3y ago[deleted]
- 486sx33 3y agoThis is reality, fortunately or not. How can you change this? Push back about specifics that won’t work, but in large terms. Example. Well we could build that, but in order to monetize it, it would cost xxx monthly which would require a gross sales increase of xxx just to break even. You may not know gross profit margin, but your exec does. So focus on costs along with strong technical reasons as to why something is ridiculous. Programmers hate being asked “how much time will this take”. This needs to be utilized and flipped around - like your crazy ass idea will consume 5000 core programmer hours which will set back the follow priorities and we can’t see a use case.