'If I had to guess, I'd say that is the main "skill" being lost'(to endure frustration).
I think this might be true for you, but for less experienced and new developers, well, they actually won't get to that stage because their 'learning' is basically prompting and they have nothing to forget nor remember. And that might be bigger issue.
It's a simple project but it doesn't have the usual AI code style to me. It reads instead like someone getting the hang of networking in C#. Incidentally, this is OP's first public C# repo.
yeah maybe, I guess it's fine, I meant no disrespect for the person learning. I can see some git issues so probably a new dev showcasing.I just don't understand how the hn posts work. Shouldn't there be some upvoting of stuff to be on the main page, or it was just released so it appeared?
For what it's worth the HN algorithm is a pretty complex, so I'm still oversimplifying but ti's more about the rate a story gains score than the points themselves. You can get just 5 votes in the first minute you're up and make the front page, which is more or less what this did.
We, as developers are currenty using a technology where:
- we add things like 'You are an expert developer/DBA/{whatever}'
to improve its performance
- we add things like 'please' to make it work better
- we no longer code, we write novels that describe code(features)
- we pretend to be doing technical work, when all we do is write english,
often yelling and cursing at the technology
From the wannabe millionaire perspective that looks at devs and engineers like expenses, I get it.
You write what you want and you are promised to get it.
But as developers we need to push back and point out few things, beacuse of professionalism and safety:
- To describe a feature and get it, there are only 2 ways:
- LLM is soooo amazingly good and knows not just to code,
but what you need, what you meant and what you didn't mean,
it knows your business, knows your clients it knows everything,
it works alone it is amazing.
This will never happen, and certainly not with this technology.
- You are a technical user that is able to describe to llm exactly what you want,
all the important steps, and all the edge cases and important stuff.
Then you review it's code, fix it, prompt it more and so on.
In this case, there are several big issues:
- you already need to be a fairly experienced technical person
(which kind of beats the whole LLM point)
- you need to prompt the shi* out of it to make it work
- you need to spend many a hours debugging issues around code you didn't write
- you don't remember the code cause you didn't write it
- how can you add new features if you didn't write the code? Tests?
If LLM wrote them what's the point?
These are pretty serious roadblocks, why aren't people talking about them? Why the fuc* are we doing todo apps instead?
If llm's do everything what about new concepts, programming languages,paradigms?
Are we supposed to use same forms, code block for everything forever?
That might even be a good thing if the code was well written!
But the crux of it is, programming is technical, if you don't write code you
are not programming and are not meant to be churning out code. People could get hurt.
And llm is not at fault, you are, check the contracts and warnings.
If you are not programmming and are instead prompting, you
should think about switching to alternate carrer like a novelist or scriptwriter.
All is good, I just kind of wanted to ask you, did you actually buy the ticket and board the AI train?
We're seeing AI-assisted proofs, drug discovery, and novel materials & methods.
> novelist or scriptwriter
That's interesting, because in some sense the book or screenplay is a "program" to persuade someone to suspend belief, or to finish reading it and "go to" the next step (acquire film rights, update their worldview, etc).
ffs, to find out what figures from the past thought and how they felt about the world, maybe we read some of their books, we will get the context. Don't prompt or train LLM to do it and consider it the hottest thing since MCP. Besides, what's the point? To teach younger generations a made up perspective of historic figures? Who guarantees the correctness/factuality? We will have students chatting with made up Hitler justifying his actions. So much AI slop everywhere.
It's great to have .NET ecosystem expanding.
I am a .NET dev, and I still use web optimized for mobile as my mobile platform(where applicable). Tried MAUI and all the other stuff, just doesn't cut it for me. You can make an app using it, but I would rather not to. The best 'mobile platform' for me was blazor hybrid, but then again - if it's already blazor why not go full web...I guess it depends on the 'seriousness' of your mobile application. If I had to develop a complex mobile app, I might choose another language framework, cause MAUI uses XAML and MVVM stuff that is quite a big overhead IMO.
"just use postgres" is an excellent advice. How about incidental complexity and ridiculous limitations of an ORM?
Time spent learning how to use an ORM can better be spent 'refreshing' your SQL knowledge.
Also, when you learn how an ORM works, you still don't know proper SQL nor how do databases works, so when you switch language now what, you quickly take a course on another ORM?
SQL is a language, ORM is not,it's just ' an entire layer of code that your application doesn't really need' and in some applications you could never ever use an ORM.
It is rather clear that I am the only one in this discussion who recently had to write code that synchronizes data that I do not control with an SQL database. Everything is easy in toy applications, where you have your USERS table with First_Name and Last_Name.
Seems like it could also be useful in planning combat(strategic) actions ad hoc, given limited resources, but I guess military already has some other tech for this...
I think this might be true for you, but for less experienced and new developers, well, they actually won't get to that stage because their 'learning' is basically prompting and they have nothing to forget nor remember. And that might be bigger issue.