While personally this excites me: the idea that I can build a custom software that fits that specific problem is quite amazing.
But on company level I see it as a risk: suddently you might have 50 new small apps created by people who might not even work at the company who are not constantly tested for security/privacy ... but more important who once done are not pushing the frontier of how a much better solution might be in that area cause nobody is putting time into them. So as time passes by this has the risk to become legacy software used to run your business. yes of course you can point an AI to all of them and prompt it to make them better but that means focus on that instead of your core business.
Maybe we will see solutions appearing to manage this kind of tech debt.
Not the OP but I think in case of scanning and tagging/summarization you can run a local LLM and it will work with a good enough accuracy for this case.
I did not crunch any numbers but I do think self-reliance with a high standard of living that means wanting and having access to everything from produce to luxury goods at a reasonable price for the majority of people cannot be achieved so easily.
You of course say self reliance on essential resources and I still think for most countries that could be very expensive very fast. People are complaining about the high costs specifically of the essential products when their prices are raising. Without a serious rethinking of our society we cannot probably fix that. And nobody is willing now to vote and agree to suffer for a generation to fix this system.
IMHO when toddlers say mama they really understand that to a much much bigger degree than any LLM. They might not be able to articulate it but the deep understanding is there.
So I think younger kids have purpose and associate meaning to a lot of things and they do try to get to a specific path toward an outcome.
Of course (depending on the age) their "reasoning" is in a different system than hours where the survival instincts are much more powerful than any custom defined outcome so most of the time that is the driving force of the meaning.
Why I talk about meaning? Because, of course, the kids cannot talk about the why, as that is very abstract. But meaning is a big part of the Why and it continues to be so in adult life it is just that the relation is reversed: we start talking about the why to get to a meaning.
I also think that kids starts to have more complex thoughts than the language very early. If you got through the "Why?" phase you might have noticed that when they ask "Why?" they could mean very different questions. But they don't know the words to describe it. Sometimes "Why?" means "Where?" sometimes means "How?" sometimes means "How long?" .... That series of questioning is, for me, a kind of proof that a lot of things are happening in kids brain much more than they can verbalise.
> Requires learning sig block's unique DSL syntax.
This is an interesting proposal. But for posterity I am going to critique the critique on the website about Sorbet:
Sorbet is Ruby and while it has a DSL that is no different than any other gem providing methods or objects to use. For example you can define a type and assign it to a Ruby constant. Because Sorbet is Ruby.
In general I would say any type system has its own syntax when you go deep into it and need more than this param has this simple primitive type and the method returns this simple primitive type. So you have to learn a DSL and the syntax of a type system.
Because the number of state where a program can be is so huge (when you consider everything that can influence how a program runs and the context where and when it runs) it is for the current computation power practically infinite but yes it is theoretically finite and can even be calculated.
In some definitions (that I happen to agree with but because we wanted to save money by first not properly training testers and then getting rid of them is not present so much in public discourse) the purpose of testing (or better said quality control) is:
1) Verify requirements => this can be done with formal verifications
2) Validate fit for purpose => this is where we make sure that if the customer needs addition it does not matter if our software does very well substraction and it has a valid proof of doing that according with specs.
I know this second part is kinda lost in the transition from oh my god waterfall is bad to yeyy now we can fire all testers because the quality is the responsibility of the entire team.
(coming from a country where having guns at home or seeing a civilian with a gun is very very strange and an huge emergency so maybe my question is stupid)
IF the government decides to use violence against you do you really have a chance with a gun? or 10?
I'm not claiming you'd be safe even with a gun. I'm not claiming there is any real government you are safe living under given a long timespan (maybe longer than even your own lifespan, but still these skills are passed down in families so breaking the chain during 'safe' times is still harmful).
To your specific question, probably not, but the better question is whether you have more of a chance with or without a gun? If you look at the Warsaw Ghetto Uprising for example, having a gun bought those people hours to days, which is better than nothing. Of course if you look at places like Chechnya, it bought them outright years that they were able to obtain independence from the brutality of Russia (even if not from their own brutality) as a result of militia activity in the first Chechen war.
Here are four small things to remember when working with Ruby:
1. Everything is an object and the main thinking is that you send messages to objects not call methods on objects. This is very important and the core of how the language works and moreso important when reading Ruby code.
2. `false` and `nil` are falsey. Everything else is truthy when used directly in conditionals. Eg: if variable will go on true-branch when variable is anything else than `false`/`nil`. Else it will go on the else-branch.
3. Start irb (the interactive console) and use <object>.inspect + <object>.class to see what is happening. Ruby has great introspection. Remember the first thing I said here (everything is an object) so you can inspect almost anything.
4. In Ruby paranthesis are optional. Eg: user.upgrade_to "admin" is actually user.upgrade_to("admin")
But on company level I see it as a risk: suddently you might have 50 new small apps created by people who might not even work at the company who are not constantly tested for security/privacy ... but more important who once done are not pushing the frontier of how a much better solution might be in that area cause nobody is putting time into them. So as time passes by this has the risk to become legacy software used to run your business. yes of course you can point an AI to all of them and prompt it to make them better but that means focus on that instead of your core business.
Maybe we will see solutions appearing to manage this kind of tech debt.
reply