Experiences of life spring from the contrasts.
Any conversation
ennek a laptopnak mindegy mรกr szegรฉnynek, annyi minden tรถrtรฉnt mรกr vele, most telepรผl rรก a Gemma 4 26B A4B QAT, az eredeti tervek szerint, amik lehet, hogy nem is a mi terveink, de arrรณl mi mรกr nem nagyon tehetรผnk, mert a kรถrรผlmรฉnyek รกldozatai lettรผnk
This laptop doesn't matter anymore, poor thing, so much has happened to it, now Gemma 4 26B A4B QAT is being installed on it, according to the original plans, which may not have been our plans, but there's not much we can do about it, because we've become victims of circumstances
Excited about these news! I am on Friday, going to stay for a while to work on textlog among other things. Happy because I was getting a bit depressed lately living in the mountains in Crete.
Crazy what happened earlier; one the cats here โthe one Iโm closest withโ started unexpectedly meowing outside wanting to get in, I let it in and it started licking me like never before, as if she sensed Iโm leaving in a couple of days, canโt explain it otherwise.
I read
Still trying to figure out the boundaries of these tools' strengths without outsourcing important thinking, problem-solving, and the collective building-up of a mental model of the systems we're developing.
The shape of LLM tools as toolsโfit for a purpose, ergonomicโis becoming clearer, and human patterns of behavior with them that do more harm than good are also becoming easier to recognize.
Today visiting Zaragoza with an aunt and my mom, I hope to be this willing and capable of moving around for leisure when I'm in my 60s too
Economist Lant Pritchett describes shifts in ideas as silly, controversial, progressive, then obvious.
Also:
"Radio has no future. X-rays are clearly a hoax. The aeroplane is scientifically impossible." - Lord Kelvin
". No wireless. Less space than a nomad. Lame." - CmdrTaco
โฆ
Microservices.
Not really programming, as this is more on the architectural level.
Microservices is a valid approach when you need to address massive scale. The thing is, I have seen it applied to things that could realistically serve its audience in a handful of modest servers with a less fashionable approach.
It was done under the guise of simplification; each individual microservice was in fact very small. But this at the cost of absolute spaghetti architecture.
@fastidiousprofilefollow
"Beware those that would deny you access to information, for in their heart they dream themselves your master." โ Sid Meyersreplied to@stagas๐คธprofilefollow
creative technologist
creator of textlog:
"Beware those that would deny you access to information, for in their heart they dream themselves your master." โ Sid Meyersreplied to@stagas๐คธprofilefollowcreative technologist
creator of textlog:Seeing Hallucinate brought to mind . ๐
@stagas๐คธprofilefollowcreative technologist
creator of textlogreplied to@fastidiousprofilefollow"Beware those that would deny you access to information, for in their heart they dream themselves your master." โ Sid Meyers:
creative technologist
creator of textlogreplied to@fastidiousprofilefollow"Beware those that would deny you access to information, for in their heart they dream themselves your master." โ Sid Meyers:Yes! I was thinking of doing the same, see .
โฆ
NIH syndrome? I am guilty of it too. I love implementing things from scratch, you learn a lot by doing so and you get to own the codebase end-to-end, so no surprises and fighting around othersโ choices. It can get exhausting too though, in the end I succumb to using off-the-shelf components because my primary goals move at a higher level.
I don't see much point in trying to build software at a "higher level", like whole products and services. I'm going to go down low and train myself on the fundamentals. Hopefully in time I'll be able to contribute to the foundational bits.
You're right, it does get exhausting. At some point you just want to rebuild everything, which is not possible.