Comments URL: https://news.ycombinator.com/item?id=47795251

Points: 2

# Comments: 0

* This is an excellent alternative to Sonnet - which was my daily driver. I'm glad I tried GLM 4.5. You won't find any difference.

* My context usage per session was about 50% with Sonnet earlier, but it fills up fast with GLM, and I hit 80-90% often. Could be the lower context size that is hurting.

* Sonnet used to be very painful to work with as the context size goes beyond 80% (hence my habit of shorter conversations). GLM holds itself well even until the last bit of remaining context. Does not deviate from the assigned task.

https://x.com/nileshtrivedi/status/1901512841318072572

(I am not the tweet author)

Stratus3D has been working on the golang rewrite for almost a year now. That is a lot of improvements working seeing the light of the day in this release.

He has also been the most active maintainer on asdf for close to a decade now (that’s also how long I’ve been inactive after the initial year of work).

There are a tonne of alternatives for those interested in retro-gaming devices.

There is also a sub-reddit for these discussions (r/sbcgaming) [2]

Devices made by Anbernic and Miyoo are good. There is also the new Gamekiddy Pixel. These existing devices are usually available at around $50-85 and are much cheaper than ModRetro’s $199 price point.

[1] - https://youtu.be/QmA20GTr8XI

[2] - https://reddit.com/r/sbcgaming

Just got the game to read the source code. Looks like Steam requires that I install the game in order to view the source, and that isn't possible because I am on a Mac. Hopefully some day :)

I like the fact that you have a lifetime plan. Given that this is a mobile app, having a lifetime plan is easier to pay-and-forget.

Hope you find success with this app.

The only plugins under the asdf-vm github org are for Ruby, Node.js, Elixir and Erlang, because those are the only languages I needed.

The initial integration is usually straightforward, but the maintanence of these seemingly simple API wrappers is what bites back in the long run.

With having lots of integrations, these are the usual failure points:

1. Teams find it hard to keep track of all the changelogs across APIs.

2. Failing at [1] means that API changes get noticed much later and having to cram the work into product development cycles.

The kind of person you seem to envy are people who are most likely pattern-matching against their past experience. I attribute this quick thinking to having come across those same/similar problem statements earlier. But getting there requires a good understanding of the problem space. This can only be done by spending time in the problem space and paying attention to details.

When working on a new problem these days. I feel like I slow down too. I now tend to go for the details. What I cannot make up in speed, I make up for with detailed solutions, thinking from the user's perspective, staying aware of trade-offs, watching out for unhandled scenarios, etc.

I also document all my work. Whenever I start working on a problem/ticket/issue, I create a new note in my personal note-taking tool. I document the commands, the new findings, etc.

Fun fact: For a limited time, I fulfilled the role of a Product Manager at my recent workplace. The engineers I worked with loved the amount of detailing in my product specifications. This was the result of slowing down and paying attention to the details. The above qualities/choices also resulted in me playing the implicit role of QA for the team. The concept of "implicit roles" is explained pretty well in this blog post on the StaySassy blog [1]

I try to compensate my slowness with attention to detail, clear communication and better documentation.

Attention to detail is as good a quality as quick thinking. I like this way better.

P.S: I actually wrote a long comment in response to this thread and then turned it into a blog post for myself [2]

[1] https://staysaasy.com/management/2021/01/21/Step-Back.html

[2] https://www.define.run/posts/details/

Hugo is fun and very extensible. I love that it is a single-file binary that I can download and use without bothering about dependencies.

When I moved away from Jekyll, I built a Hugo theme for my blog as my first for-profit hobby project - https://define.run/lucid-theme/

Lexity.com looks like a Yahoo service and maybe this is the analytics being collected. AFAIK pg's site is still hosted on Yahoo.

Thank you for the feedback. I’ll ping the team to let them know about this thread.

The plugins were kept as separate repos - like Heroku Buildpacks, because I never had the time to vet/review them. I had written plugins for Ruby, Node.js, Erlang and Elixir because those are the ones I wanted. I did not expect the project to be active this long or have these many contributors, maintainers and users.

We’ll bring back the readme in the repo with usage instructions.

P.S: Author here. Not an active maintainer except helping clean issues

Comments URL: https://news.ycombinator.com/item?id=25654220

Points: 1

# Comments: 0

* https://nowthisnews.com/stories/paralympic-swimmer-builds-ma...

* https://www.lonelyplanet.com/stories/5-destinations-to-see-w...

What I don't see:

* I visited the home pages of those sites. I'm not sure how to open up stories if I were an internet user just passing by.

* I don't see a way to exit the stories experience other than clicking a link/article

* How to open a story from any web page on a desktop (It is called "Web Stories" so I assumed a few things)

This seems to be build on top of AMP:

* https://amp.dev/documentation/guides-and-tutorials/start/vis...

* https://amp.dev/documentation/guides-and-tutorials/integrate...

The maintainers take good care of the project and I admire the energy and consistency that maintainers like Trevor Brown have.

I try really hard to contribute sometimes by responding to issues and closing them. But that is all the energy I can spare for the project.

At this point I would rather focus on anything that pays money than work on something purely for the sake of open source.

What I wish I knew 12yrs ago:

* Money is not a bad thing to take/have. * Irrespective of whether projects are opensource or paid, they need to be sustainable.