|
|
|
|
|
|
by captain_coffee
147 days ago
|
|
|
Yes OK, but that was not the point that I was trying to make. You are developing in a language + framework that you are not familiar with, without having any human feedback in the process at all - see where I am going with this? Even with a quarter of a decade of experience you are still in what can basically be reffered to as uncharted territory. |
|
|
- I've never used a new language or framework before? Nope
- I've never used both a new language and a new framework at the same time? Nope
- I've never tried to do real work in a new language and new framework that I'm not particularly familiar with? Nope
- I've never shipped work I've done in a new langauge and new framework that I'm not particularly familiar with? Nope
What specifically do you think is so magic about Ruby and/or Rails that you think I won't have encountered something similar in some other form - in some other language or framework - before?
And do you not think that the reviewing and changes that I am making to the code, the prompting I'm doing, the decisions I'm making about which changes to integrate and which to ignore, etc., as a human being, count as feedback?
At the end of the day I'm building a web app, and soon enough an API, and the concerns in building this web app and API are exactly the same as the concerns I've had in building other web apps and APIs.
The only difference is the language and the framework, and I've learned new languages and frameworks before. And, although I'm using an LLM to help, I've been doing that for the past 3 years using different stacks and the only notable difference is that LLMs are quite a lot better at helping to develop software than they were 3 years ago.
So how is this uncharted territory?
---
And, as an aside, not an issue you've raised but one I commonly see on HN: people moaning about job ads demanding X years of experience in this or that framework or language (with the parody being that the desired framework or language has only existed for X years, or maybe not even that long), and how this isn't really relevant to whether an experienced software engineer can do the advertised job or not. I happen to agree with that perspective but here's the thing: you can't have it both ways. Either that's true or it's not true, and I'm operating (as I have done before and as you can probably tell) on the basis that it is true.