3 ms·

Two thoughts: - I admire your honesty of telling this. AI is quickly becoming something you rather want to hide. - I would never want to work at such a compan

Two thoughts: - I admire your honesty of telling this. AI is quickly becoming something you rather want to hide. - I would never want to work at such a company. If I wanted to engineer by human language I would be a politician or a manager. If I wanted to babysit an automaton, I would have been a factory worker.

buzzbyjool 1y ago
for your second point, I understand your position, but I strongly believe that it's the future of coding. Coding was a way to translate a machine language to something more understandable, AI coding is simply the next step.
fragmede 1y ago
> If I wanted to babysit an automaton, I would have been a factory worker. I wonder if horse carriage drivers said the same thing about the advent of cars. Telling the LLM build me a login page instead of laboriously looking up example code in docs and retyping stack overflow snippets is definitely a different way of working, but thinking that makes someone a politician seems like a bit of a stretch.
- exceptione 1y ago
  The difference is determinism. A technical inclined person wants to build things from first principles. Assembly or a higher level language are in that nature the same. Now, most humans are social beings and rather play social "games" with language. That is why technical people used to be called nerds, because they are the exception. Engineers by heart (those of their own choosing rather than because of economical pressure) love the technical reasoning part of their brain. Now a stochastic model that may lie to you, or respond differently on how your word it today, is a completely different kind of work. It is in principle not engineering, but rather some kind of managing or influencing.
  - myk9001 1y ago
    What's your backup plan if you don't mind sharing?
    - buzzbyjool 1y ago
      what you mean by backup plan ? We produce proper code like node.js or similar that is backup and proceed in a normal pipeline. Just the production of the code is different.
      - myk9001 1y ago
        > Just the production of the code is different. Just like you, I think prompting LLMs to produce code for us is the future of the profession. Not necessarily a fan, this is just how I see the reality of it. The person I'm replying to feels this ruins the profession for them, if I'm reading their comment right. Hence the question. Edit: Oh, you're the post's author. Thanks for sharing and I hope the business is going strong.
        exceptione 1y ago
        I don't understand why you attract downvotes, tried to upvote you, but to answer your question: I have no real backup plans, but I can see that my (and my peers) knowledge, design sensitivity and architectural skills will become an even more real scarce asset, especially when there is a surge of vibe coded projects. In the case of OP however, I think he has found a niche (I assume) in which, between deep applications and throw away code, the balance tilts over to the latter. So this is the domain of MS Power Apps, low code prototypes, and Power BI reports. And so, potentially, his personnel was already more apt to not dislike how the nature of their work changed.
        buzzbyjool 1y ago
        You’re absolutely right that there’s a spectrum between deep applications and throwaway code. But I wouldn’t place what we’re doing in the Power Apps / low-code / Power BI category. The systems we’re building with LLMs (at Easylab AI) aren’t quick prototypes or business dashboards — they’re fully functioning SaaS platforms with scalable backends, custom business logic, API orchestration, test coverage, and long-term maintainability. The difference is: they’re authored through agents, not typed from scratch. And to your point about design sensitivity and architecture becoming scarce — I couldn’t agree more. When LLMs handle 80% of the syntactic work, what’s left is the hard stuff: system thinking, naming, sequencing, interfaces, data flows. That’s exactly where our team shifted: less “builders,” more “designers of builders.” It’s not easier work — it’s just a different level of abstraction. Thanks for the reply, sincerely. It’s good to talk about this without defaulting to hype or fear.
- Magma7404 1y ago
  Cars are reliable and when they break down we can fix them ourselves. I can do that too with any compiler or tool. AI is still and will always be a black box that could hallucinate any moment. You could say the same with software embedded in new cars, but I would reply that it's the kind of cars that I wouldn't want to drive. Also the car makers have a legal responsibility to make sure it behaves well on the road. AI companies have no responsibilities and put a lot of hidden stuff (like censorship) in their products which makes them unacceptable to me. LLMs are unreliable tools by definition which is not a good thing compared to what I use all the time.

buzzbyjool 1y ago

for your second point, I understand your position, but I strongly believe that it's the future of coding. Coding was a way to translate a machine language to something more understandable, AI coding is simply the next step.

fragmede 1y ago

> If I wanted to babysit an automaton, I would have been a factory worker. I wonder if horse carriage drivers said the same thing about the advent of cars. Telling the LLM build me a login page instead of laboriously looking up example code in docs and retyping stack overflow snippets is definitely a different way of working, but thinking that makes someone a politician seems like a bit of a stretch.

exceptione 1y ago
The difference is determinism. A technical inclined person wants to build things from first principles. Assembly or a higher level language are in that nature the same. Now, most humans are social beings and rather play social "games" with language. That is why technical people used to be called nerds, because they are the exception. Engineers by heart (those of their own choosing rather than because of economical pressure) love the technical reasoning part of their brain. Now a stochastic model that may lie to you, or respond differently on how your word it today, is a completely different kind of work. It is in principle not engineering, but rather some kind of managing or influencing.
- myk9001 1y ago
  What's your backup plan if you don't mind sharing?
  - buzzbyjool 1y ago
    what you mean by backup plan ? We produce proper code like node.js or similar that is backup and proceed in a normal pipeline. Just the production of the code is different.
    - myk9001 1y ago
      > Just the production of the code is different. Just like you, I think prompting LLMs to produce code for us is the future of the profession. Not necessarily a fan, this is just how I see the reality of it. The person I'm replying to feels this ruins the profession for them, if I'm reading their comment right. Hence the question. Edit: Oh, you're the post's author. Thanks for sharing and I hope the business is going strong.
      - exceptione 1y ago
        I don't understand why you attract downvotes, tried to upvote you, but to answer your question: I have no real backup plans, but I can see that my (and my peers) knowledge, design sensitivity and architectural skills will become an even more real scarce asset, especially when there is a surge of vibe coded projects. In the case of OP however, I think he has found a niche (I assume) in which, between deep applications and throw away code, the balance tilts over to the latter. So this is the domain of MS Power Apps, low code prototypes, and Power BI reports. And so, potentially, his personnel was already more apt to not dislike how the nature of their work changed.
        buzzbyjool 1y ago
        You’re absolutely right that there’s a spectrum between deep applications and throwaway code. But I wouldn’t place what we’re doing in the Power Apps / low-code / Power BI category. The systems we’re building with LLMs (at Easylab AI) aren’t quick prototypes or business dashboards — they’re fully functioning SaaS platforms with scalable backends, custom business logic, API orchestration, test coverage, and long-term maintainability. The difference is: they’re authored through agents, not typed from scratch. And to your point about design sensitivity and architecture becoming scarce — I couldn’t agree more. When LLMs handle 80% of the syntactic work, what’s left is the hard stuff: system thinking, naming, sequencing, interfaces, data flows. That’s exactly where our team shifted: less “builders,” more “designers of builders.” It’s not easier work — it’s just a different level of abstraction. Thanks for the reply, sincerely. It’s good to talk about this without defaulting to hype or fear.
Magma7404 1y ago
Cars are reliable and when they break down we can fix them ourselves. I can do that too with any compiler or tool. AI is still and will always be a black box that could hallucinate any moment. You could say the same with software embedded in new cars, but I would reply that it's the kind of cars that I wouldn't want to drive. Also the car makers have a legal responsibility to make sure it behaves well on the road. AI companies have no responsibilities and put a lot of hidden stuff (like censorship) in their products which makes them unacceptable to me. LLMs are unreliable tools by definition which is not a good thing compared to what I use all the time.