Live data from Hacker News

It's time to become an ML engineer (2022)

blog.gregbrockman.com

41–50 of 53 posts

Re: It's time to become an ML engineer (2022)

#41
> All that being said, AI is not for every software engineer. I’ve seen about a 50-50 success rate of engineers entering this field. The most important determiner is a specific flavor of technical humility.

Oh, give me an f-ing break and spare me the self-congratulation.

Re: It's time to become an ML engineer (2022)

#42
post #20

I 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 these things without depending on someone else.

Re: It's time to become an ML engineer (2022)

#43

Earlier 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?

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)

#44

Earlier 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.

But you shouldn't do some stuff you can't do properly at all, not quickly and not slowly. As a layman, you can't sign a contract in a language you don't speak, even if you have a whole year, unless you can become more-than-fluent in that language in a single year. That's just not something you should do, and the AI isn't reliable enough to help you with it. That's what a legal department is for.

Re: It's time to become an ML engineer (2022)

#45
post #23
post #4

Earlier 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. ^^

No, but if "productivie" becomes one of the variable names eventually used in legacy work . . . full engineer achieved!

Re: It's time to become an ML engineer (2022)

#46

Earlier 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?

Similar to "real work," a "real job" is a definitional problem that attacks people's senses of self.

Re: It's time to become an ML engineer (2022)

#47
post #20

I 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…

Good point, it definitely isn't hands off from what I have seen. Just fewer people needed to manage those integrations.

Re: It's time to become an ML engineer (2022)

#48
post #18
post #4

Earlier 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.

We never have any proof or source for that, and when we have one (like the Devin thing) it’s always a ridiculous project in JS with a hundred lines of code that I could write in one day.

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)

#49

Earlier 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…

I would never in my whole life sign anything in a foreign language that I don’t understand. It’s the perfect example of what AI is: let’s do anything that looks like a job well done and fuck it. That is not convincing. It’s suicidal.

Re: It's time to become an ML engineer (2022)

#50
post #3

Nearly 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…

OK, but React development is one of the simplest development tasks out there. It’s probably the most popular UI framework with the most data for the LLM model to generate off existing solutions. Low hanging fruit that also provides the least value to companies since react developers are a dime a dozen.

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.

Post reply on HN