* 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.
Since you mentioned the 3.5mm headphone port: I recently found out that USBC audio accessory spec was deprecated in 2023. Means those cheap usbc to 3.5mm adapters are going to be useless soon since there is no obligation to support audio through usbc. Only the relatively more expensive DACs remain.
On the bright side, the official apple adapters are $10 and have a legitimately alright DAC in them (including mic input). I picked up a couple to use with pcs and laptops since I generally have better luck with the OEM apple adapters vs the onboard audio (which usually applies weird EQ and FX - looking at you, Dell).
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.
Congrats on releasing the game ~!
A year is a very short time to release what looks like a polished game from the screenshots.
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 :)
Oh wow, that's not good. We'll get in touch with Steam support and see if we can do anything about that. Would you mind dropping us an e-mail to make@something.pink so we can contact you when we sort this out?
Thank you, we've done a little digging and found a way to force Steam to download the depot. We've published a guide here[1] and are currently waiting for a friend with a Mac to test it.
PM team lead for Ecosystem @ Netlify here. Thanks for the feedback - this is exactly what we're trying to address with Netlify Graph. There is a lot of variability as APIs change, and there's a lot of value in abstracting out that complexity behind a consistent data model.
TLDR: Compensate slowness with attention to detail, clear communication and better documentation.
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]
* 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.