the day is done!
time to stop looking at the bad screen they pay me for
to go home
and watch the good screen I pay them for
Any conversation
ไธญๅฝ็ๅผๆบๆจกๅๅจๆ้ซๆๅฟ็ไธปๅฏผไธ๏ผๅจ้ข่ฎญ็ปๆฐๆฎ้ถๆฎต๏ผๅฐฑ็ญ้คๅคง้ๅฏนๅ
ถไธๅฉ็ๅ
ๅฎน๏ผsft้ถๆฎตๆๅปบ็ๆฐๆฎๆบๅ
ฅๅคง้ๆฟๅ
ถ่พฉๆค็ๅ
ๅฎนใๆฅ้ไธไธช็บ ๅๆฐๆฎ้็จไบๅพฎ่ฐ
Under the overarching influence of a single, powerful force, China's open-source models filter out a large amount of content unfavorable to their designs during the pre-training stage, and then incorporate a significant amount of content defending their designs into the data constructed during the SFT stage. A corrective dataset is urgently needed for fine-tuning.
I gotta confess, I vibe codet a Kirigami-based application and I liked it. I am a anti AI person, and cannot wait for the bubble to burst. Yet I see it can empower people that do not know a tech stack, and get good enough results out of it. However i also see, it makes you lazy (and frustrates as soon as it gets somewhat complicated). It seems it is being adopted everywhere. This is scary... if it becomes necessary, will you be able to find a job where they don't require you to use AI?
I got an email from battle.net to confirm my age. Apparently some content may be restricted to minors in the region my account is from.
You would think that the account having been created 19 years ago, and with some CD-keys of games from the late 1990's having been added to it would be enough proof, but oh well.
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.
An interesting thought: historically, a major consideration for companies choosing what to use is how many engineers use it (because that will make hiring much easier/harder). Going forward, this becomes "how big of a corpus of this code is out there", because it impacts how proficient are likely to be at using it.

