Absolutely annoying to have it assuming that I want to use this when I type workflow in the prompt. Like thats not already a thing in half of the software projects
Author here. I'm surprised to see this surfacing now. I just wanted to clarify, since apparently the post doesn't do a good job at it, that what I discussed there is not a methodology I advocate for. The point of the post was: ok, since there are organizations mandating to maximize speed by reducing time spent on typing code (or even mandating to maximize agents usage), is there a way we can meet that requirement while still preserving the rigor somewhere else?
This was a follow up to a previous article[1] and the pair tried to express what I still think today (using AI daily at work): every time I use AI for coding, to some capacity I'm sacrificing system understanding and stability in favor of programming speed. This is not necessarily always a bad tradeoff, but I think it's important to constantly remind ourselves we are making it.
Is there a recommended modern day, non mac specific, equivalent to those "Macintosh Human Interface Guidelines" linked at the beginning of the article?
I started with prelude[1], I wanted something batteries included to use as my main editor right away, but not as structurally different from vanilla as Doom or Spacemacs. Then after a couple of years I rewrote my config line by line looking at what prelude did and keeping only what I needed.
I’m happy with result, but this was 7 years ago so there may be better options than prelude to do something similar today.
I did try to build a public facing news aggregator with a similar ux but I couldn’t pull it off purely based on client side state (and I didn’t want to do user management)
I have the same issue, the chronological nature of feeds kind of breaks this flow. It feels like there’s a missing piece, like a standard to browse older content from a blog. I Wrote a bit about this here: https://olano.dev/blog/web-anthologists/
As a non native English speaker/writer there are a bunch of errors I miss, no matter how much attention I pay and how much I proofread, and these tools are useful to catch those.
Most of the "structural" events of the story are true, most of the scenes are made up or pastiche. If you're interested in the facts, I suggest taking a look at the sources at the bottom, especially the Mark Ferrari interviews: https://youtu.be/ri4_3P2Oh14?feature=shared
I considered adding them (also considered adding links to the book page) but I ended up preferring the uncluttered titles only version. (I know it makes it inconvenient to lookup the book).
Depends on how your blog is generated. Static generators like jekyll have plugins for this[1], but it’s also easy enough to generate it by hand with an xml template [2]. Wordpress, substack and other platforms generate it by default afaik.