2,797 karma · joined April 28, 2010
> Code is not an asset, it's a liability.
> Every line must be maintained, debugged, secured, and eventually replaced. The real asset is the business capability that code enables.
> The skill that survives and thrives isn't writing code. It's architecting systems. And that's the one thing AI can't do.One suggestion to make it more usable:
If I hover over a word in the foreign language, I should instantly see the equivalent word(s) in English highlighted. This way I can look up the words I do not know know very quickly, w/o interrupting the listening experience.
Yes, I know I can click on a word to see what it means, but it's too slow for the purpose of identifying its English equivalent.
The cognitive reality of AI, and more specifically of AI+Humans in the context of a social and globally connected world, is on a higher level of sophistication and can unfold much faster, which in turn might generate entirely unexpected trajectories.
There are so many potential trajectories going forward for things to turn sour, I don't even know where to start the analysis. The level of sophistication an AI can achieve has no upper bound.
I think we've had a good run so far. We've been able to produce software in the open with contributions from any human on the planet, trusting it was them who wrote the code, and with the expectation that they also understand it.
But now things will change. Any developer, irrespective of skill and understanding of the problem and technical domains can generate sophisticated looking code.
Unfortunately, we've reached a level of operational complexity in the software industry, that thanks to AI, could be exploited in a myriad ways going forward. So perhaps we're going to have to aggressively re-adjust our ways.
Can’t help but wonder about the reliability and security of future software.
Given the insane complexity of software, I think people will inevitably and increasingly leverage AI to simplify their development work.
Nevertheless, will this new type of AI assisted coding produce superior solutions or will future software artifacts become operational time bombs waiting to unleash the chaos onto the world when defects reveal themselves?
Interesting times ahead.
Given the insane complexity of software, I think people will inevitably and increasingly leverage AI to simplify their development work.
Nevertheless, will this new type of AI assisted coding produce superior solutions or will future software artifacts become operational time bombs waiting to unleash the chaos onto the world when defects reveal themselves?
Interesting times ahead.
Works with base16, btw.
Is anyone who has exited the tech world still reading HN? What's it like on the outside?
[1] https://www.visualcapitalist.com/cp/charted-most-popular-u-s...
* What are NIFs: https://www.erlang.org/doc/tutorial/nif.html
* Using Rustler in Production: https://discord.com/blog/using-rust-to-scale-elixir-for-11-m...
"almost 14,000 lines of raw PHP mixed with inline HTML, CSS in <style> and raw JS in <script> tags"
and making $60,000/month. [1] Talk about non-pretentious stacks.[1] https://en.wikipedia.org/wiki/Stratospheric_aerosol_injectio...
[1] https://techcrunch.com/2023/03/07/worldcoin-cofounded-by-sam...
Re: Rust - I've been trying out basic examples, simple web servers, etc; nothing too fancy. But it just seems too ceremonious to get even the most basic things done. I own the book "Rust in Action", I just didn't have the proper time to go over it.
Although at first, some unfamiliar design decisions annoyed me, for they were not well explained in the tutorials I was learning the language from – e.g `arg: value` as a shortcut for `[{:arg, value}]` in function arguments and other places – over time, I've grown to love and appreciate the language and I now more or less regard it as an elegant programming language put together by a thoughtful person with great programming taste.
The Phoenix framework is a great bonus point if you want increased productivity for writing web apps. I don't miss Python at all.
Elixir rests on the shoulders of giants though, and the Erlang/OTP is yet another elegantly engineered piece of technology, enabling one to develop concurrent, distributed and fault tolerant systems with ease, and in this regard I think the Erlang/Elixir ecosystem takes the crown. The actor model is simple, yet very powerful.
For reference, I've also been learning Nim and F#, and they're also pretty unique and well designed languages in their own ways. I love Nim's fast compilation times, efficiency and expressiveness and F#'s powerful type system which enables one to develop domain models with ease. I've also been occasionally taking stabs at Rust, but it always feels just a tad too complex for my brain. I'll continue playing with it though, maybe it will eventually make sense.
Ultimately, every design decision is also a tradeoff. I don't think we'll ever have a perfect, human designed language.
My dream language would probably be a combination of Elixir and F# though, a language with an advanced and powerful type system, functional programming and the actor model as the building blocks. I guess fast compilation times à la Nim wouldn’t hurt either. :)
Perhaps benchmarks should be compared on equal footing, say, with the default release flag or all optimizations turned on, otherwise they're improper.