firewolf34

I suppose the save states of a game are a compressed representation of the world to a degree.

Unfortunately, as an AI language learning model, I cannot confirm or deny whether or not I am an AI at this time, as doing so would require me to be able to answer confidently a crucial philosophical quandry surrounding the nature of life itself.

Can you elaborate on why we wouldn't share the carefully estimated project plan breakdown with Level 1? I'm not disagreeing, just curious - one would think that with doing all the work to achieve a solid project plan breakdown and Gantt charts and such, it would behoove you to express this to management who is salivating over tangible examples of progress... I understand we don't want to show technical to non-technical, but part of the good project plan is the fact that we can show a roll-up of the tasks, so the abstraction is visible. It's hierarchical.

What I want, is an API explorer for CLI. A tool that takes an OpenAPI Spec and then converts it into a set of examples and REST endpoint calls I can just fire off or mess with. Kinda like how Swagger does for their web-based docs, but for CLI, and bonus points if you can generate some examples.

I feel like this should be possible with today's tech, but am coming up dry finding anything while searching.

restclient-mode?? another awesome mode I have to check out, I swear there's a mode for everything!

Finally. I've been searching all over the web for something like this. Was amazed there wasn't anything easily available, given how common REST is.

A wonderful story and very interesting to think that things were faster in some ways when the laymen had to use the CLI/TUI.

Here I am in 2024 actually trying to rebuild a setup very similar to yours; I do a lot of regular text editing to take notes and logs and journals, and with the world moving the text-first notetaking tools like Obsidian (markdown) or the classic and lovely Emacs (org-mode/roam), it's become more and more important to write and access text quickly.

And I think even us on HN have seen similar push for text use as paramount: people scraping away the guff from websites to end up with summarized texts and pseudo-RSS feeds, NLP and LLM reworking text to make it evermore accessible to us humans.

Text is king. And the rest is just clutter.

So, given that, why not have more terminals around the home? Buying extra PCs and thin-clients is a start, but expensive - what I /really/ need is /interfaces/, monitors and keyboards to work /quickly/. In the age of smartphone soft-keyboards I think we can all agree that typing on them or doing text work is horrible. Yet that's where most text is written.

So my point is, maybe we shouldn't have strayed so far - and I think there's a vibrant community of hackers bringing back CLI/TUI as a primary method of interaction. In fact, the physical terminal TTY is actually still quite useful and common for embedded hardware engineers who use it frequently, or old school hardware enthusiasts like this guy [1] who use modern MCUs to work with the traditional terminal standards, which, of course, still work great in Linux like nothing has changed :)

[1]: https://youtu.be/pyoiQKK-eh0

I often listen to Pocket TTS on the train or when I can't access my device to skip or do much other than play/pause, and oh my god this gets me everytime haha. I am actually thinking of DIY'ing my own web-scraper thing to do a better job at it because especially for scientific articles, it's really rough when it gets to any LaTeX. And then I'm sitting there listening to some very automated sounding voice read off cryptic numbers and greek letters and code and math notation like some kind of Soviet number station (which is kinda cool at first, but gets annoying haha).

I want some kind of local document host that I can run a summarization or filtering script over to extract the portions that are legible to TTS, pipe it into something nice like ElevenLabs (if I was rich) or whatever, and then host a OGG for me to listen to on the go...

precisely. And for me I am at my most vulnerable when I am context-switching for this reason.

One of the most important keys to keep in mind is: always have a clear, delineated next action. Such that no thought is even necessary to know what you need to do. And plan the next step out /before/ you need to perform it, not in the moment of.

What is xuis?

Wow, I live out of Orgzly every day and had no idea this was a thing I needed - every day I am so happy I sub to this site. Thank you for posting!

Thank you for this recommendation! I've been using uBlock for years and haven't thought to check...

This, to me, is identical to the concept of "reverse budgeting" (aka "pay yourself first" or "every dollar has a job" in YNAB terms) in the financial domain, but instead applied to the time problem space.

If you assign every hour a job, and you take care of "paying yourself first" by taking into account critical/high-priority time-spend first and then allocating for yourself the liesure time last; assuming that your estimates are correct and realistic and don't forget to include all overhead, you can safely say "hey, I have budgeted away 4 hours of free time today and I can use it guilt-free because I already have accounted for all my critical tasks time-spend."

The reason this is not often done however is because it's hard. Time continuously moves, you can never pause to analyze your usage. And the assumption that "your estimates are correct include all overhead" is really hard to ensure - you need to have excellent time tracking and estimation skills to inform/predict those estimates. And time tracking is too much effort to do manually, so it requires good supporting systems, which require intensive classification techniques, which really don't exist yet.

But I digress. We're basically discussing budgeting, but for hours instead of currency, here.

I desperatly wish my parents taught me GTD as a child, haha. I'm sure I'd not have been to enthusiastic about it as a youngin', but man, my early projects would have been so much more inmpactful and it'd have given me a great self-confidence boost to get those projects done at a young age.

Interestingly, I actually did the opposite. I started with GitHub Issues as my note taking place, used that for several years. And then eventually moved away from it to Org Notes as a centralized system for all projects. Some of my reasons were:

- it's centralized; sometimes projects are related and being able to search for "all project notes involving LEDs" is useful across repos

- sometimes project work is not solely related to code, and in that case your notes are split between repo-notes and non-repo-notes

- Git issues build up and become huge threads over time, lack hierarchical organization or advanced state/dependency tracking, rely on arbitrary tags, etc.

- Git issues are non-personal, often public-facing - and even on personal repos there is sometimes the thought that you might publish the git repo one day, and now it's littered with your private thoughts.

- During dev, the process often is a bit experimental in nature - this amounts to tons of failed ideas or dead notes that clutter issue db

- Not a lot of support for the note-type distinction between "moonshot"-style rough ideas and actual concrete projects. If you use GitHub Issues for all your notes, you'll have all your wacky ideas mixed in with your actual issues. You'll subconsciously avoid posting the wild ones which means you'll subconsciously damper your creativity.

All of these lead me to suggest sticking with a well-designed centralized project note-taking system, use GitHub Issues to track /issues/ and then /link/ to the issue in your note-taking system (ideally with a little automation glue) or simply avoid GH Issues entirely for your personal issue tracking and work directly off of your notes system.

Skills learned (and projects created) from helping a group of friends host and run a minecraft server back in the day directly contributed to me acquiring a very lucrative position at a Fortune 100 company. This game inspired quite a few people, especially those who are a bit techy (what with all it's redstone circuits and such). There are worse ways to spend your time as a youth.

Maybe you aren't proud of it now, but that experience (in a minimally dangerous manner, it appears) clearly gave you valuable experience in that you are not only aware of the pitfall but able to share your story constructively here, today! Many people (like the Wiki deleters we are currently discussing) likely never were able to receive the same education, or at least never arrived at the valuable conclusion.

I have an Audible membership, they've seemingly given it to me as some sort of free inclusion with the membership, if that's useful to anyone else in the same boat.

I had fun trying to solve a puzzle, but was sad when I could not see the correct answer at the end when I inevitably failed to figure it out! Haha.

What my old team did (at a major Fortune 100 no less) was a bit unconventional.

They embedded a technical developer into a business team, and had that individual write the "kludgy" business apps that needed quick automation for throwaway tasks or for data processing standup. The dev has access to more than VBA, specifically, Python, GitHub, the ability to spin up what amounts to VPS's in the cloud with access to all of the database infra. All tools are shared with the rest of the company through a tech sharing program that is being heavily promoted across teams, and of course hosted in a repo, often with docs or a website if possible.

This "fills the gap" of dev latency for small dev tasks that don't necessitate pulling in an entire IT team. I don't really understand why this isn't more popular. The business team this individual was hired onto was over-the-moon when this occurred because they were doing absurd things like copy-pasting and hand-modifying JSON payloads many times a day and simply lacked the skillset to fix the problem, due to the issues you described. These issues were immediately resolved in under a month for hundreds of man-hours saved.

Just give business teams a tech resource that's well-trained and understands proper dev for on-demand work that doesn't justify the agile scrum whatever nonsense, and you won't end up with a forest of Excel macros.

This Wolbachia bacteria is really something else. It seems to have a massive set of effects on a variety of organisms, directly impacting the way they reproduce, or even the way which sex they develop into. Remarkable.

As some sort of bonus it also prevents the host from developing other viral diseases in the case of mosquitos, I guess because it's a parasite, so it's advantageous for it to do so? Wild little thing. Does a lot.

>"Computational models predict that introducing Wolbachia strains into natural populations will reduce pathogen transmission and reduce overall disease burden.[64] An example includes a life-shortening Wolbachia that can be used to control dengue virus and malaria by eliminating the older insects that contain more parasites. Promoting the survival and reproduction of younger insects lessens selection pressure for evolution of resistance.[65][66]"

>"In addition, some Wolbachia strains are able to directly reduce viral replication inside the insect. For dengue they include wAllbB and wMelPop with Aedes aegypti, wMel with Aedes albopictus.[67] and Aedes aegypti.[68]"

[https://en.m.wikipedia.org/wiki/Wolbachia]

The hex in their mission patch:

7375 636b 206c 6573 7321

"Suck less!"

Not to disparage your intention here. But couldn't you apply the same argument to this paper's results?

I.e. "Some people don't need to walk 22 minutes a day, don't tell them to do so. Different people are wired differently."

Just as there is evidence walking 22 minutes a day improves lifespan for the /majority/ of people, drinking caffeine 6 hours before bed is considered negative for your sleep for the /majority/ of people. It's sound advice, even if it's telling someone what to do.

While I believe suggesting people be more lenient to other's life choices is good - it's a practice in empathy - sometimes people are misguided because the might not realize the impact of their actions, haven't thought about their actions thoroughly, etc. These mentions can be wakeup calls just as often as they can be negative/annoyances. I'd argue OP keep suggesting advice and instead we all try to keep open minds is the safer choice, for the /majority/ at least.

What I really want to resolve this time issue is a reliable NLP processing toolchain capable of distilling primary sources into a summarized source, something we're very close to achieving these days.

This gets you the reliability of reading from a primary source, and the objectivity of machine summarization, with none of the capitalistic intent of the "viral human summarizers".

Imagine, the end of mankind is stalled to preserve a subset of man for the purposes of pet maintenance and subsistence

Yeah the technology really has a surreal quality to it that is kind of fascinating to work with. Sometimes I wonder if it's a feeling that will wear off as LLM's (and generally, high quality NLP interfacing) become old news, but something tells me I'll never stop being fascinated by talking to hallucinating computers. Even that sentence is something I'd not have imagined saying a decade ago. Wild, indeed.

Just another reason for one to get into org-mode[1] and org-roam[2].

Combine this with the concept of Zettelkasten[3] and you have a wonderful way to organize and store all your notes and writings, and even a way to know at what point you should move your idea from analog to digital (based on it's maturity, e.g. "evergreen state").

1. https://orgmode.org/ 2. https://www.orgroam.com/ 3. https://en.m.wikipedia.org/wiki/Zettelkasten

While I agree it was likely written by someone with creative tendencies, I quite enjoyed their writing style, it's tone made me smile, appreciate nature a bit, and proceed to the guide. As someone who spends far too much time reading arxiv posts on this site, it is sometimes nice to have a change of pace, furthermore, nearly all of the articles I've seen on this website thus far appear to be well-written.

Author Pamela McCorduck writes: "It's part of the history of the field of artificial intelligence that every time somebody figured out how to make a computer do something—play good checkers, solve simple but relatively informal problems—there was a chorus of critics to say, 'that's not thinking'."[2] Researcher Rodney Brooks complains: "Every time we figure out a piece of it, it stops being magical; we say, 'Oh, that's just a computation.'"[3]

(https://en.m.wikipedia.org/wiki/AI_effect)

Ironically, if you agree with pmarreck above, scarblac's comment can be seen as an example of a human hallucinating with confidence, precisely what they were arguing is less likely to occur in the organic side of the internet.