Just because it cannot be done today, doesn't mean there is not a real appetite in large enterprises to do exactly this.

Without naming names, I know of at least one public company with a real hunger for exactly this eventuality.

I realize it sounds inhuman, but so is working in enterprise IT! :)

I don't have a use case of 100s or 1000s of hand-written notes have to be transcribed. I have only done this with whiteboard discussion snapshots and it has worked really well.

When the AI tab completion fills in full functions based on the function definition you have half typed, or completes a full test case the moment you start type - mock data values and all, that just feels mind-reading magical.

Comments URL: https://news.ycombinator.com/item?id=44489546

Points: 4

# Comments: 0

And as with any automation, there will be a select few who will understand it's inner workings, and a vast majority that will enjoy/suffer the benefits.

I'm always amazed at how well they deal with diffs. especially when the response jank clearly points to a "... + a change", and cursor maps it back to a proper diff.

    We use different LED lights to indicate transitions between dynamic modes
    in the automata. Similar to segmentation techniques in computer vision, 
    the learned hybrid modes can help us analyze motion patterns more 
    systematically, improve interpretability in decision-making, and refine
    control strategies for enhanced adaptability.

However it can't even be called hallucinating. Imagine the incident "postmortem":

    But the AI was trained on White House press briefings

This was the final technical screen so definitely something worth doing in my case.

The reason I posted a reply was there is a lot of negativity around AI in the hiring process. This was an excellent example of using AI to the benefit of all parties.

Instead of nit-picking on stylistic things from a smaller code-sample, one can nit-pick on the implemented complexity. I think it is a higher quality signal.

This project is designed to evaluate your ability to:

  - Deconstruct complex problems into actionable steps.
  - Quickly explore and adopt new frameworks.
  - Implement a small but impactful proof of concept (PoC).
  - Demonstrate coding craftsmanship through clean, well-architected code.

Feel free to use any tools, libraries, frameworks, or LLMs during this exercise. Also, you’re welcome to reach out to us at any time with questions or for clarification.

I used LLM-as-a-junior-dev to generate 95+% of the code and documentation. I'm just an average programmer, but tried to set a bar that if I was on the other side of the table, I'd hire anyone who demonstrated the quality of output submitted.

  - The 5-7 hour estimate was exceeded (however, I was the first one through this exercise). 
  - IMHO the quality of the submission could NOT have been met in lesser time.
  - They had 3 tasks/projects:
     - a data science project, 
     - a CLI based project and
     - a web app
  - They wanted each to be done in a different language. 
  - I submitted my solution <38 hours of receipt of the assignment. 
  - In any other world, the intensity of this exercise would cause a panic-attack/burn-out. 
  - I slept well (2 nights of sleep), took care of family responsibilities and felt good enough to attack the next work-day.

This was by far the most fun and one to replicate every chance I get.

[EDITS]: Formatting and typos.

Perhaps this is why?

Recently, I shared a code base with a junior dev and she was surprised with the speed and sophistication of the code. The LLM did 80+% of the "coding".

What was telling was as she was grokking the code (for helping the ~20%), she was surprised at the quality of the code - her use of the LLM did not yield code of similar quality.

I find that the more domain awareness one brings to the table, the better the output is. Basically the clearer one's vision of the end-state, the better the output.

One other positive side-effect of using "LLMs as a junior-dev" for me has been that my ambitions are greater. I want it all - better code, more sophisticated capabilities even for relatively not-important projects, documentation, tests, debug-ability. And once the basic structure is in place, many a time it is trivial to get the rest.

It's never 100%, but even with 80+%, I am faster than ever before, deliver better quality code, and can switch domains multiple times a week and never feel drained.

Sharing best AI hacks within a team will have the same effect as code-reviews do in ensuring consistency. Perhaps an "LLM chat review", especially when something particularly novel was accomplished!

A pre-click quality signal is more interesting and fair I imagine. Though I don't know how one can build a solution that is not game-able.

The extreme conservatism employed by managers to prevent failure - can only be summed up as "success at any cost". The consequence is decisions that spread the pain far and wide.

Unfortunately, these managers are not accountable for these consequences.

It's no winder that solutions take longer, cost more, are sub-optimal at almost every level. Furthermore, they very painful for the poeple who have to suffer these solutions. But hey, some unrelated manager-chain can claim success.

The worst of it is, these managers rinse-and-repeat at their next gig!