SingAlong

Same in Vietnam. Just refresh the page. It’ll get you through.

Former small phone person here: I went from a small iphone to a large one just to substitute not having to carry around my ipad. I really wish iphone fold is here sooner.

Been using this for two days now. Notes below:

* 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.

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

(I am not the tweet author)

Great to see this here!

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).

I just watched their YouTube video [1]

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

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 :)

I love the design. Thank you for making this.

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.

I wouldn't go by whether a plugin is first-party or third-party.

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.

From having maintained 60+ API integrations for a B2B business, I can see how Netlify Graph (or previously OneGraph) solves a real problem.

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.

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]

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

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

I would recommend adding Doks to the list - https://getdoks.org/ Doks is an opensource documentation and blog theme. Looks amazing.

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/

I see those requests too but my adblocker takes care of it.

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

I just woke up to find this thread on home page and read all the comments.

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

Thank you for sharing this. Even though it is a compliment for you and your project, it made my as a solo maker.

They do allow merchants to sell subscriptions - https://help.shopify.com/en/manual/products/subscriptions

I just tried a few things. Sharing notes here incase anyone wants an overview. I tried visiting a few sites that had stories:

* 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...

This resonates with me. Although a relatively small and unknown project, I’m in phase-9 for asdf version manager.

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.

TBH because Ansible is what I’ve been using for a long time.

And based on what FunnyLookinHat mentions in another comment, Terraform seems to offer a lot less. I have no first-hand experience with Terraform to confirm that.

I'm building a bunch of opinionated Ansible playbooks + tooling, with a Heroku-like experience.

I'm working on a command-line deployment tool that deploys to DigitalOcean and AWS LightSail (to start with). This is based on my experience deploying apps.

I expect to finish the remaining work in the next few weeks. Can I contact you to try it out? (My email is on my profile)

Hey Caylan, The video is good.

I understand when you say creating screencasts is hard. It took me sometime to get to a point where it takes me just an hour to record a 5min video (can also be read as sarcasm, because I find it hard too).

This looks nice. I’m looking forward to using this as a page/list of blog posts/links.

I love this.

The part where socks are used to dim the bulbs brightness is funny and nice way to move forward.

I’ve been looking for project ideas to showcase during wedding. It seems like a really large friendly audience to demo games and other fun experiences. This project is inspiring.

I use git commit messages for this. When I stop working, my commit messages look like these.

“Completed ABC; TODO XYZ”

“WIP ABC; TODO XYZ”

When I get back, all I have to do is check the previous commit.

BBK Electronics owns OnePlus, Oppo, Vivo and Realme.

These brands are super popular in China, India, Vietnam and rest of South East Asia.

I have a 10min attention span for intense activities like reading. I use this to my advantage to do I might otherwise not do.

* Reading: I take my Kindle to the toilet.

* Solve quiz on Brilliant.org during office commute

* Listen to audiobooks before sleep

* When waiting for the next meeting, I read bookmarked articles.

--- My Lessons: ---

* It is very important to stop doing something once I realize I have no more juice.

* My total learning time per day is around 1hr on best days.

* Takes 1hr to reach office. So during cab rides, after a quiz is done (10-15min), I nap.

* When zoned out in and realize I'm doing random wild-wild-internet-reading, I immediately turn tech off. I just talk to people (work or casual chat).

* During times of silence, I observe things around me. I learn new things about stuff that has been around me for a long time. I put these observations to use when I draw (I use Procreate app on iPad). For example: I observed reflections in water and attempted to draw a reflection https://www.instagram.com/p/BrxmF1enz87/

GraphQL is great for the frontend, but moving to GraphQL involves both people and tech issues. Common mistakes made when using new technologies are made all over again.

* Watch out for bad implementation of the GraphQL API (this will definitely result in bad performance).

* Design the GraphQL schema that you want the user to see/perceive. Not every object or field in your database needs to be exposed via the API the way it is.

My workplace is currently moving a huge monolith into a bunch of manageable components. Each of these components has its own GraphQL endpoint. Using schema-stitching, these are being stitched together into one endpoint for API users.

As a result of our codebase, we've tried GraphQL in:

* Ruby (graphql-ruby) - WATCHOUT Relay arguments for connection fields are not exposed to the library user. So basically you have to implement your own Relay-compliant stuff if you need access to the pagination arguments from Relay. Also, documentation is broken.

* Python (graphene) - We've had no issues so far. We worked around it.

* Node.js (Apollo GraphQL) - OH MY BUTTERFLIES. So far, this is the ONLY library I have come across that is polished and has plenty of documentation.

* Elixir (Absinthe) - My coworker worked on this part. He did not complain. So I'm assuming he had no issues.

The "Learn * in a day" joke applies to GraphQL. As simple as GraphQL looks for the client-side, it is beast of a job to build a GraphQL backend that is optimized for production.

Servers-side implementation of GraphQL is not very well documented apart from hello-worldly examples. Most of the knowledge found online is about client-side usage.

Due to poor documentation/examples provided, ramping up people with GraphQL is hard. Most first iterations I've had to review were slower than our REST APIs because of unoptimized code. Sitting down for a few minutes solves that problem.

To ramp up people at work place, I ended up having to do this:

* Ask people to use the GitHub v4 API to checkout GraphQL.

* Make them build a GraphQL server for a blog app.

* Dive straight into whatever feature/API they would build.

* Review their work a few dozen times and show them optimization tricks.

My most valuable lesson: When in doubt, dig into the source of these libraries.

Thank you ~!

[P.S.A] This might not matter a lot, but just incase: The PDF link on this website links to a 2017 version (vs 2011 version on the parent thread).

I have learnt to combine pomodoro with GTD to create routines.

My routine is simple and takes a total of 4hrs. I leave the rest of time to other unplanned things that come up.

Been attempting to follow the routine for a couple weeks. As a result I have noticed these changes:

* Consistent reading habit.

* Haven’t even thought about watching TV for more than a week.

* Had lunches and dinners on time.

* Slept by 10:30pm

* Have not refreshed HN frontpage every hour (I have forgotten about HN for an entire day sometimes).

If anyone is interested, I have details about my routine and the reason behind my simple routine - http://hashnuke.com/gtd-workflow-2.html