100%. My team started using graphite.dev, which provides AI generated PR descriptions that are so bloated with useless content that I've learned to just ignore them. The issue is they are doing a kind of reverse inference from the code changes to a human-readable description, which doesn't actually capture the intent behind the changes.
I just cancelled my Kagi subscription over the weekend. Some of the ideas in the article resonate (the dev team seems spread way too thin) but I also decided that the main product just wasn't distinct enough. The lens and quick answers features were nice, but otherwise the search results were not that different from Google's -- Having just switched back, I haven't noticed a significant difference.
I also think this product might be a bit too late. GPT4 has been out for over a year now, and it's changed how I look for answers. I tried FastGPT but like the author I found it lacking. As it stands, Perplexity feels more like the future of search than Kagi.
I’m disappointed, but I can’t say I’m surprised. I once tried to contact their support team after getting effectively locked out of my account, only to have the support form return a 5XX error upon submission. I dropped them right then and there.
> During a spacewalk, Mission Control in Houston warns Explorer's crew about a rapidly-expanding cloud of space debris accidentally caused by the Russians having shot down a presumed defunct spy satellite
Try showing them some clips from Kitboga [1] — he talks to tech scammers (usually pretending to be an old lady) with the goal of wasting their time, and demonstrating how most tech scams work.
One of the biggest selling points of these services is that you can view your live video feed from anywhere via mobile device -- A savvy tech enthusiast might be able to create such a setup by hand, but the majority of people wouldn't know where to begin.
Reading "The Design of Everyday Things" will give you a sense of the basics -- After that try learning a popular frontend-web framework (like Bootstrap / Foundation) which follows lot of the industry-standard UI practices out-of-the-box. Also checkout things like WAI-ARIA / WCAG, which outline accessibility standards on the web.
Choose a documentation source-of-truth (Confluence, etc) and keep a changelog[1]. I've also seen a dedicated email group (i.e. [email protected]) used for tracking non-code changes.
Ideally, from the get-go. Your system and documentation should be produced & grow in-parallel. At worst, before any team members with key (undocumented) domain knowledge leave.
Usually that requirements list comes directly from the hiring manager telling the recruiter "here are all the attributes of an ideal candidate", who in turn posts it in the job description verbatim. Not much thought goes into it beyond that.