"Questions cover HTML, CSS, JavaScript, databases, and Node." Ah yes, as if Web development = All coding
Show HN: Dev atrophy test – Can you still code without AI?
31–40 of 42 posts
Re: Show HN: Dev atrophy test – Can you still code without AI?
#32Earlier quoted context omitted.
computer science is not social science if your code doesn't work it doesn't work you can't bullshit a computer for people that are doing social science it's an issue but they where way past the point of no return already so it doesn't really matter
I’d argue that computer science is on a gradient between social science and physics.
I'd argue that anything that has science at the end isn't :)
Re: Show HN: Dev atrophy test – Can you still code without AI?
#33Earlier quoted context omitted.
computer science is not social science if your code doesn't work it doesn't work you can't bullshit a computer for people that are doing social science it's an issue but they where way past the point of no return already so it doesn't really matter
Software engineering is way more of a social practice than you probably want to believe. Why is the code like that? How are people likely to use an API? How does code change over time? How can we work effectively on a codebase that's too big for any single person to understand? How can we steer the direction of a codebase over a long timescale when it's constantly changing every day?
Yes that is very true but social science is more of a social practice than computer science
If you run your organization badly, you'll run into problems sooner, than if you are in social science, where you just have to say all the buzzwords and they'll just rubberstamp you true
If you are arguing that my point is that computer science would be 100% falsifiable and social science is 0% falsifiable then you're argument is a bit of a straw man
Re: Show HN: Dev atrophy test – Can you still code without AI?
#34Re: Show HN: Dev atrophy test – Can you still code without AI?
#35So as someone who's not written Javascript in a decade, this on the face of it seems wrong to me:
Your example correct answer to "Write a function that returns the sum of two parameters" is
function myFunction(example) {
example
}
Re: Show HN: Dev atrophy test – Can you still code without AI?
#36Earlier quoted context omitted.
computer science is not social science if your code doesn't work it doesn't work you can't bullshit a computer for people that are doing social science it's an issue but they where way past the point of no return already so it doesn't really matter
Software engineering is way more of a social practice than you probably want to believe. Why is the code like that? How are people likely to use an API? How does code change over time? How can we work effectively on a codebase that's too big for any single person to understand? How can we steer the direction of a codebase over a long timescale when it's constantly changing every day?
> Why is the code like that? How are people likely to use an API? How does code change over time? How can we work effectively on a codebase that's too big for any single person to understand? How can we steer the direction of a codebase over a long timescale when it's constantly changing every day?
At which point you are studying project management theory, or whatever you call it
Re: Show HN: Dev atrophy test – Can you still code without AI?
#37Re: Show HN: Dev atrophy test – Can you still code without AI?
#38Re: Show HN: Dev atrophy test – Can you still code without AI?
#39"Questions cover HTML, CSS, JavaScript, databases, and Node." Ah yes, as if Web development = All coding
You are right, it should just focus on React really.
Re: Show HN: Dev atrophy test – Can you still code without AI?
#40So as someone who's not written Javascript in a decade, this on the face of it seems wrong to me: Your example correct answer to "Write a function that returns the sum of two parameters" is function myFunction(example) { example } Is the atrophy coming from inside the house?
The vibe giveth, the vibe taketh.
This worked but ai wants to rewrite whole files all of the time so it broke. Our designer fixed the issue now.