Oh, give me an f-ing break and spare me the self-congratulation.
It's time to become an ML engineer (2022)
41–50 of 53 posts
Re: It's time to become an ML engineer (2022)
#42I find this take interesting in the present. I work at $BIGCO that has done lots of ML in house for many years. I have noticed more and more ML projects being killed because their work is superseded by external model vendors. Why spend millions on a team to build a new model, when you can pay thousands to rent someone elses?
Re: It's time to become an ML engineer (2022)
#43Earlier quoted context omitted.
Some jobs it's more. I had to sign a 140 page contract of foreign language legalese. Mostly boiler plate, but I had specific questions about it. Asking questions to an AI to get the specific page answering it meant I could do the job in 2 hours. Without an AI, it would have taken me 2 days. For programming, it's very good at creating boilerplate, tests, docs, generic API endpoints, script argument parsing, script one…
But what you're doing isn't a real job. Who hands someone who doesn't speakt the language a contract to sign? Don't you have a legal department that does this job for you and has people that are specialists for that? Also, what are you going to do if the AI answered inaccurately and you signed a contract that says something different then what you thought?
Re: It's time to become an ML engineer (2022)
#44Earlier quoted context omitted.
But what you're doing isn't a real job. Who hands someone who doesn't speakt the language a contract to sign? Don't you have a legal department that does this job for you and has people that are specialists for that? Also, what are you going to do if the AI answered inaccurately and you signed a contract that says something different then what you thought?
You are confusing not being able to do something well with being able to do it quickly.
Re: It's time to become an ML engineer (2022)
#45Earlier quoted context omitted.
Curious to hear what kind of work you do. Because there are definitely fields where productivity as 10x'd because of AI tools.
being 10x more productivie with ai doesn`t mean that someone is now a full engineer. ^^
Re: It's time to become an ML engineer (2022)
#46Earlier quoted context omitted.
Some jobs it's more. I had to sign a 140 page contract of foreign language legalese. Mostly boiler plate, but I had specific questions about it. Asking questions to an AI to get the specific page answering it meant I could do the job in 2 hours. Without an AI, it would have taken me 2 days. For programming, it's very good at creating boilerplate, tests, docs, generic API endpoints, script argument parsing, script one…
But what you're doing isn't a real job. Who hands someone who doesn't speakt the language a contract to sign? Don't you have a legal department that does this job for you and has people that are specialists for that? Also, what are you going to do if the AI answered inaccurately and you signed a contract that says something different then what you thought?
Re: It's time to become an ML engineer (2022)
#47I find this take interesting in the present. I work at $BIGCO that has done lots of ML in house for many years. I have noticed more and more ML projects being killed because their work is superseded by external model vendors. Why spend millions on a team to build a new model, when you can pay thousands to rent someone elses?
It's a good question, and there are sometimes good answers. Does someone else's model understand how to standardize and interpret your company's data? Will they notice and tell you if something isn't looking right? What if the model needs to change to account for opportunities or risks from evolving data sources or business environment? Building in-house can help ensure that an organization has the competencies to do…
Re: It's time to become an ML engineer (2022)
#48Earlier quoted context omitted.
Curious to hear what kind of work you do. Because there are definitely fields where productivity as 10x'd because of AI tools.
Please give us a source for the x10.
Give me some refactoring in a C++ code base with 100k lines of code, and we’ll be able to talk.
Re: It's time to become an ML engineer (2022)
#49Earlier quoted context omitted.
Seriously? 10x? Either those were cushion jobs or you oversold your claim
Some jobs it's more. I had to sign a 140 page contract of foreign language legalese. Mostly boiler plate, but I had specific questions about it. Asking questions to an AI to get the specific page answering it meant I could do the job in 2 hours. Without an AI, it would have taken me 2 days. For programming, it's very good at creating boilerplate, tests, docs, generic API endpoints, script argument parsing, script one…
Re: It's time to become an ML engineer (2022)
#50Nearly two years on from this article's publication, 'AI' tools are still as useless as ever for productive work.
> Nearly two years on from this article's publication, 'AI' tools are still as useless as ever for productive work. Fully disagree. When developing I use llm's all the time. its far quicker for me to ask an llm to build a react component than for me to type it and have to remember all the little nuances for a technology I use a couple of times a year. When proto typing things or doing quick one offs, using an LLM mak…
Also, one could argue that the LLM provides less value since a simple Google search for most react questions can produce a very viable answer, since 90% of what most React developers do has already been done and shared on the Internet.