So, I'm watching two shows right now - Silo and Attack On Titan. I'm nearing the end of S3 on Silo and have just finished S3 of AOT. The parallels between the two are interesting but the contrasts are more interesting, namely how much more intricate AOT is.
Any conversation
code quality is about coupling.
coupling is not a technical property of the code bytes.
code acquires its meaning in contact with the cultural environment, and coupling is about meaning.
two constants with no semantic relationship are nonetheless coupled in pragmatics if they refer to the same domain concept.
if your goal is to minimise the time integral of future work, you must understand your domain: it decides which lines will need changing.
to carve up a codebase is to carve up the world.
I have a toddler.
I come home from work, cook, feed, clean, wash up. We read stories and play. I put him to bed.
Then I put something on the television and my wife and I scroll on our phones until she goes to bed.
I am not so careless with the little free time I have.
I continue to scroll until about 1 am.
The next morning I do it again.
On the weekends, I get to drink wine.
You would not download a car...
You would not upload a collection and ask the user to log in now...
Send api requests 1998 style.. lightweight and without tracking
github.com/alainnothere/mailBoy
news.ycombinator.com/item?id=50359814
โฆ
i dont think its all talk, these are smart people that have been in ai since the 2000s, and they raise good points. current incentive structures are very dangerous long term
they too have every incentive to exaggerate because they are selling safety and/or books on the topic. I donโt believe we wonโt see it coming. Any issues that will manifest will be very visible and weโll have plenty of time to mitigate their impact.
they could be making a lot more money by just working at ai firms i fear. the thing that got me worried the hacking incidents lately, huggingface etc.
if the capabilities consistently outspeed the development of safety measures, and if the private arms race logic continues, i dont think this is a good spot to be in long term
@fastidiousprofilefollow
"Beware those that would deny you access to information, for in their heart they dream themselves your master." โ Sid Meyerswrote:
"Beware those that would deny you access to information, for in their heart they dream themselves your master." โ Sid Meyerswrote:@stagasprofilefollow
creative technologist
creator of textlog, will it possible, on mobile, to be able to tap on โcardsโ. That is, make the posts area โtapableโ.
creative technologist
creator of textlog, will it possible, on mobile, to be able to tap on โcardsโ. That is, make the posts area โtapableโ.@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:Great idea, implemented here! Thanks for the suggestion.
I've been building a Markdown variant called Zd that's focused on extensibility and simplicity. I'm curious what you would change about Markdown if you were designing it from scratch, what challenges you face as a user, or what you wish were easier to do when incorporating Markdown into your own projects.
Definitely tables are cumbersome.
Yeah, 100%. That is completely something I am punting on currently. It would be easy to just copy over the solution from (extensions to) Markdown, but it's hard to entirely narrow in on both what tables ought to do and how to make them do it.
If you had a magic wand, what would you have them be more like?