I sit in meetings all day long, I roll my eyes and die a bit and synergize and circle back
inner life
sacrosanct
outer face
smiling stone
no need to rush:
executives
don't need to work
just synergize and circle back
Any conversation
I find myself building bespoke tooling for my own and workflows these days, not only because of the obvious reason of software being so much cheaper to build, but also because there are SO MANY options for solving any given problem that it feels impossible to evaluate all of them.
If it's not a crucial piece of tech for a work problem then it often feels like paving my own way is both cheaper mentally (kind of amazing that's true these days) and probably a better fit.
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.
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.
ไธญๅฝ็ๅผๆบๆจกๅๅจๆ้ซๆๅฟ็ไธปๅฏผไธ๏ผๅจ้ข่ฎญ็ปๆฐๆฎ้ถๆฎต๏ผๅฐฑ็ญ้คๅคง้ๅฏนๅ
ถไธๅฉ็ๅ
ๅฎน๏ผ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.

