Seems easily digestible and approachable for a specific target audience.
247 karma · joined April 28, 2011
Seems easily digestible and approachable for a specific target audience.
My Family recently (in the last couple of years) started to breed Ragdoll cats in the U.K.
In an attempt to support what's involved in this I built Ardent for them. It covers a bunch of the day-to-day concerns (weighing and health tracking), Lineage and Inbreeding prevention, and Owner Pack generation for handovers to new Owners.
https://www.lazyvim.org/installation
Then run `LazyExtras` and you get a prompt that shows things like:
Recommended Languages: (2)
○ lang.docker mason.nvim nvim-lspconfig nvim-treesitter none-ls.nvim nvim-lint
○ lang.toml nvim-lspconfig
Hit x against a couple and you're off to the races.[lang.docker and lang.toml are examples of things you're selecting, the list after is what is being installed and configured for that thing]
For things like integrating a debugger, or to run your tests directly inline from the editor might require more customisation though.
I doubt it'll be of interest to folks here - but my Family recently (in the last couple of years) started to breed ragdoll cats in the U.K.
This has been my personal project to understand where I personally find LLMs useful as coding assistants, and where I don't. One easy to spot example is, front-end + copy. Another area I've enjoyed it is talking through how I'd design and build functionality and features ahead of time.
It's been very interesting, and is helpful to folks I care about, even if no-one else ends up using it!
I'm not trying to call out Sentry.io specifically here, I'm just using them as the example because it happened today. In fact, in general I'm a happy customer of theirs.
I'm trying to understand the motivations behind companies that aren't open about their uptime (or other issues, such as data breaches etc).
Why is it not encouraged/rewarded (or perceived as such) to be up front and open about these things? It seems that amongst the HN crowd it has been valued, and folks are appreciative and supportive of these things (vocally and with their wallets) - so why is it not more common practice?
(Note: Zero negative sentiment towards imgur here)
If all your content is consumed and presented via a third party - how does that change the nature of "content publishing".
It's the summarisation of Wikipedia and the like on steroids.
The more I've used it, the more I've disliked how poor the results it's produced, and the more I've realised I would have been better served by doing it myself and following a methodical path for things that I didn't have experience with.
It's easier to step through a problem as I'm learning and making small changes than an LLM going "It's done, and production ready!" where it just straight up doesn't work for 101 different tiny reasons.
Even then, when you start to build up complexity within a codebase - the results have often been worse than "I'll start generating it all from scratch again, and include this as an addition to the initial longtail specification prompt as well", and even then... it's been a crapshoot.
I _want_ to like it. The times where it initially "just worked" felt magical and inspired me with the possibilities. That's what prompted me to get more engaged and use it more. The reality of doing so is just frustrating and wishing things _actually worked_ anywhere close to expectations.
You can opt to not follow their rules, and they can opt to not approve your app.
You'd be better served using an example.com email address for test accounts over a test.com account, with the former being a reserved domain name and the latter being a real one.
This doesn't lead to a discussion, or informative comment threads.
You can ask for the same in return from those you're interacting with, but considering you're a brand new account seemingly created to provide a counterpoint; it felt worth calling out (with your declining Karma).
- Those that really try hard to make sure the computer cannot crash.
- Those that see the computer crashing as an inevitability, and want to ensure the appropriate behaviours are in place when it does happen.
If those are the Bose NC700, mine decided after a year to stop charging, and instead smell like melting plastic with smoke coming out of them.
That in itself wouldn't be an _absolute_ terrible thing, except their customer support was _abysmal_.
First of all they suggested I hard-reset the headphones, much to my surprise. When I emphasised that I wouldn't be plugging them in again and repeated the point about smelling melting plastic and smoke coming out, they then asked for pictures before initiating a replacement order process they'd suggested.
I explained that there isn't any visual indicators on the headphones such as melting plastic as I'd noticed it immediately, but they insisted I send them photographs anyway.
On sending them photos as asked (and clarified) they've since gone radio silent for 3 weeks, and ignored any more attempts to get in touch with them.
So yeah... I won't be touching Bose products at all in future.
Having a single version manager that manages the versions for numerous tools across different teams has been invaluable.
I’ve recently switched to using a 5G connection for home internet and whilst it’s very early days - a slight sacrifice in latency (ADSL isn’t great there either), and a daily modem restart, is a welcome price to pay for 250Mbps down/50Mbps up (at the same price point).
Please someone feel free to correct me, but if I recall correctly a lot of the improvements in Vim 8 were a result of the popularity of functionality in NeoVim?
https://n-e-r-v-o-u-s.com/shop/product.php?code=346
Edit: To clarify it relates to the title, rather than the content of the article. :D
Clicking on any of the remaining spaces results in:
Uncaught Error: what
at LogicGrid.updateKnowledge (logic-grid.js:431)
at LogicGrid.resolveCell (logic-grid.js:175)
at LogicGrid.reveal (logic-grid.js:96)
at HTMLElement.reveal (grid.js:111)
at HTMLElement.<anonymous> (grid.js:61)