flankstaek

I think this article misses a potential connection in the capitalist critique of LLMs to correlate this to the equivalent "industrialization" of coding. When a craft becomes industrialized, as is talked about here, you see the divergence in hobbyists and mass production.

I think because of the uniqueness or newness of the craft of programming - this shift hadn't actually occurred and you were seeing hobbyist programmers landing jobs and being able to output professional code by crafting it thoughtfully as there wasn't a major output difference previously. Now we are seeing that difference.

Food for thought, interesting article!

Maybe I'm "vibecoding" wrong but to me at least this misses a clear step which is reviewing the code.

I think coding with an AI changes our role from code writer to code reviewer, and you have to treat it as a comprehensive review where you comment not just on code "correctness" but these other aspects the author mentions, how functions fits together, codebase patterns, architectural implications. While I feel like using AI might have made me a lazier coder, it's made me a me a significantly more active reviewer which I think at least helps to bridge the gap the author is referencing.

Better to have loved and lost then to have never loved at all. Why not buy the Framework, support the business, and have a laptop that's making you happy while it's around?

There's no guarantee any company lasts forever. What's the point in not using something now because it might be gone in the future?

>EVs SUCK as trucks.

What makes you say that?

Usually the L stands for Libre indicating full freedom of usage of the software and that is not just "free" as a price tag.

https://www.gnu.org/philosophy/floss-and-foss.en.html

It's interesting what the "Decreasing Technologies" graph implies by omission. Assuming this means that technologies not included in that graph have been consistent through the same time period. Without a corresponding data view for "Increasing Technologies" there's not really any data on current trends.

Why do you think the manufacturers mislabeled efficiency has any relevance to how the installation team performed?

Would you mind explaining what Mdbook does in this context?

It seems like it fulfills a completely different purpose than what's being talked about here.

Location: Richmond, VA (USA)

Remote: Yes

Willing to relocate: Not likely

Technologies: ReactJS, Python, React Native, MySQL, C#

Résumé/CV: https://www.flankstaek.me/resume.pdf

email: ian@flankstaek.me

Location: Richmond, VA (USA)

Remote: Yes

Willing to relocate: Unlikely but possible

Technologies: ReactJS, Python, React Native, Unity

Résumé/CV: https://www.flankstaek.me/resume.pdf

email: ian@flankstaek.me

This letter feels as though it is overlooking a large point of contention.

>The scientists who wrote this horrible code most probably had no training in software engineering, and no funding to hire software engineers

Shouldn't the argument be, that for research that is reliant on coding models, funding be allocated to experts that can assist in creating said models (software engineers)?

Interesting to see that so many of the exemplary projects are python based. I wonder if there's any correlation there.

Cool project.

  "Also...Zwitterion is NOT a bundler. It eschews bundling for a simpler experience."

I get that, run locally, it's not bundling, but how is it not a bundler when running static builds for production?

What confuses me is their reluctance to attempt to use other third party distributors (itch.io, GOG, etc.) when Steam clearly isn't working in their favor.

http://archive.today/XirsP - Link for those who don't pay for WSJ.

[Removed]

Should get added to http://up-for-grabs.net/

I'm pretty sure the default Twitter app supports notifications on users tweets.