Kent retweeted
@hassanrahim they're trying to cut open the bird to find the song
102
2,085
16,216
935,834
Kent retweeted
Counter argument: Not only is taste subjective, it's a moving target. As soon as [tasteful thing] becomes easily replicable, it stops being tasteful.
Taste is a status game with a strong defensibility mechanism. That's why the term is so fuzzy and ill-defined. Vagueness is the whole point. It's meant to be hard to copy.
Taste is a status game with a strong defensibility mechanism. That's why the term is so fuzzy and ill-defined. Vagueness is the whole point. It's meant to be hard to copy.
I no longer see any compelling reason to believe that taste is some permanent boundary LLMs won’t cross. It’s already happening.
103
161
1,572
74,873
@SamuelBeek Thats so cool! I was referring to a very good essay from David Foster Wallace. Well worth the read: ialjs.org/wp-content/upl…
1
0
0
36
I honestly don't enjoy writing in Obsedian.
I grew up with iA Writer and Byword, and Obsedian just doesn't get anywhere close enough to meeting that experience bar.
I think a big part of it is being so reliant on clunky plugins to get a decent experience.
I grew up with iA Writer and Byword, and Obsedian just doesn't get anywhere close enough to meeting that experience bar.
I think a big part of it is being so reliant on clunky plugins to get a decent experience.
4
0
58
17,250
@kepano @kentdebruin @SGuergachi Would it be possible to make Notebook Navigator the default exporer for us blokes who use it as an configurable option?
Example, clicking on breadcrum rn leads us to the default viewer. Same for tags. It would be really nice to have the flexibility to choose our default conifg
Example, clicking on breadcrum rn leads us to the default viewer. Same for tags. It would be really nice to have the flexibility to choose our default conifg
2
0
1
126
@kentdebruin @SGuergachi tbh low likelihood of implementing three pane view since no one on the team likes that style 😅
2
0
13
587
@kepano @SGuergachi Haha interesting. I come from Apple notes. Three pane view gives me the most overview over what I’m working on in a project. But if you have no folders it’s less useful probably.
1
0
1
413
@kepano @SGuergachi my bad these were all just plugin names. Good to know that some of these are not needed anymore!
2
0
4
592
@kepano @SGuergachi A lot of them should just be build-in features, not even plugins:
Contextual typography
Better word count
Image balance
Paste image rename (In general better image features would be very useful)
And finally Notebook navigator. Would love to see a Obsidian native version of that
Contextual typography
Better word count
Image balance
Paste image rename (In general better image features would be very useful)
And finally Notebook navigator. Would love to see a Obsidian native version of that
1
0
4
1,354
I can barely navigate my are.na anymore. revisiting or adding to existing channels has become almost impossible. by sheer volume and engagement it's probably the most "substantial" thing i've ever built and it's an unmanageable mess
3
0
11
1,350
@throw_remote Make a group called “archive” and send some channels there
3
0
8
1,128
@AREdotNA @throw_remote What your stance on making archive a first class citizen in the ui, instead of this ‘hack’
0
0
0
119
why shipping 100s of prs makes sense
there's always something to improve in your product's codebase. if your goal is to make customers happy as fast as you can, it makes sense to fix those things the moment you find out about them. we're no longer limited by intelligence!
some of this is of course the result of the new way of working. ai is a net-benefit for codebases, but leaves behind more residue as people are less in tune with low risk areas. which you then have to squash by shipping more.
of course it's a little bit different for frontend/design, where the (human) thought required for the average fix is higher. but in backend land, there are always obvious bugs waiting for you to eliminate them.
i think many people would benefit from focusing on speed! it's the equivalent of the running advice to "just run more."
unless you cheat your way out, it's hard not to get to a better product/codebase/engineering skills by simply trying to put up more prs.
we're in the brief period where models still need our slight handholding and energy, which is why this advice still feels uncomfortable. but soon enough models will make the rate at which we used to evolve products feel dull.
there's always something to improve in your product's codebase. if your goal is to make customers happy as fast as you can, it makes sense to fix those things the moment you find out about them. we're no longer limited by intelligence!
some of this is of course the result of the new way of working. ai is a net-benefit for codebases, but leaves behind more residue as people are less in tune with low risk areas. which you then have to squash by shipping more.
of course it's a little bit different for frontend/design, where the (human) thought required for the average fix is higher. but in backend land, there are always obvious bugs waiting for you to eliminate them.
i think many people would benefit from focusing on speed! it's the equivalent of the running advice to "just run more."
unless you cheat your way out, it's hard not to get to a better product/codebase/engineering skills by simply trying to put up more prs.
we're in the brief period where models still need our slight handholding and energy, which is why this advice still feels uncomfortable. but soon enough models will make the rate at which we used to evolve products feel dull.
Can someone help me understand how shipping 100s PRs a day makes sense?
Why do you need to ship so many PRs in the first place?
I might just not be AI-pilled enough to understand the need for it yet, so I’m genuinely trying to understand it.
8
0
28
4,337
@vinvan As long as you can keep the product simple, and doesnt produce slob, yeah why not. It's a completely new way of working and requires a bit of a change in thinking
0
0
1
142