ayuhito

9 ms·

31.
by ayuhito 2y ago
My company used to do everything on-prem. Until a literal earthquake and tsunami took down a bunch of systems. After that, yeah we’ll let AWS do the hard work of enabling redundancy for us.
32.
by ayuhito 2y ago
Kyle is a great guy. Just to correct the timeline a little bit, I only created Fontsource after its predecessor, Typefaces (which was made by Kyle), was left abandoned when Gatsby took off. I wouldn’t say he made Typefaces specifically for
33.
go-useragent – Fast trie-based user-agent parser(github.com)
1 points by ayuhito 2y ago|0 comments
34.
by ayuhito 2y ago
I recently got a chance to find a practical use for a modified hybrid trie which was fun to implement! Lots of optimisations to go around. It’s a nifty user-agent parser for Go: https://github.com/medama-io/go-useragent
35.
by ayuhito 2y ago
As someone who has to regularly commute one of these lines… doing “nothing” does become very dull after a while. I think this thread is a little overblown. Some people will do nothing, read a book, listen to music, or nap. But the easiest t
36.
by ayuhito 2y ago
Obligatory plug for Medama, which focuses on easy self-hostability: https://github.com/medama-io/medama I think Plausible’s self-hosting is not simple, requiring unnecessarily heavy databases like ClickHouse, which can
37.
by ayuhito 2y ago
I completely agree that the self-hosting story for Plausible is overkill for most websites. So much so that I made my own that focuses on self-hostability using SQLite and DuckDB (no external dependencies, can run on a 256MB VM): https:&#x
38.
by ayuhito 2y ago
Two experienced Go devs tackle the same task, and their code will look almost identical. Two experienced Rust devs tackle the same task, and their solutions will be worlds apart. (I write both, but I do love Go for its simpleness)
39.
by ayuhito 2y ago
You may like JSDoc[1] if you just want some type-safety from the IDE without the compilation overhead. It’s done wonders when I’ve had to wrangle poorly commented legacy JavaScript codebases where most of the overhead is tracing what type t
40.
by ayuhito 3y ago
> But I wonder if building lock-in is really in their customers' interests - or theirs, if people lose faith in them. People happily (or sometimes unhappily) lock themselves in with AWS since it’s convenient and useful. And that’s w
41.
by ayuhito 3y ago
I agree with almost all the points of the author, and I absolutely have seen the benefits of journaling and writing down any future aspirations like a TODO list. > simply telling people about your future self also helps massively. Howeve
42.
by ayuhito 3y ago
I wholeheartedly agree. At most, I introduce JSDoc[1] to newer developers as standardising how parameters and whatnot are commented at least gets you better documentation and some safety without adding any TS knowledge overhead. [1] http
43.
by ayuhito 3y ago
> and then their customers sent me unfriendly email and demanded that I provide support for the tool and solve their problems Out of curiosity, what sort of tool were you offering? I’ve always heard about this but it’s never been my expe
44.
by ayuhito 3y ago
Fontsource[0] is also an easy way to self-host variable fonts via NPM packages. [0] https://fontsource.org/?variable=true
45.
by ayuhito 3y ago
Also I think Japanese companies are super risk-averse in general anyways. Not many of them hyperexpanded and overhired in COVID, so there weren’t many extra employees to layoff anyways.
46.
by ayuhito 3y ago
Also by the same author: LiteFS[0] The difference is that LiteFS is meant for high availability and low global latency, whilst Litestream is designed for disaster recovery. [0] https://github.com/superfly/litefs
47.
by ayuhito 3y ago
> You will always be one step ahead in rolling out new features and bug fixes. You may also be one step behind when it comes to infrastructure related bugs or support if you want to focus on providing the best product. Competitors who ho
48.
Fontsource(fontsource.org)
2 points by ayuhito 3y ago|1 comments
49.
by ayuhito 3y ago
I worked at a similar type of office, but I had coworkers who also had interned/worked for Rakuten. These are based on the accounts of my local coworkers, but their experiences with previous traditional Japanese companies involved stri
50.
by ayuhito 3y ago
I would say it fits in a third category. It’s a Japanese office that switched to English as its official language and hires a lot of foreign engineering talent. These types of companies are becoming more and more prevalent in Japan. It is i
51.
by ayuhito 3y ago
I worked for a Japanese corporation where each floor had different rules. One floor had an open-plan layout where people were open to chitchat, another open-plan floor that expected everyone to be quiet, and there was a floor with reservabl
52.
by ayuhito 3y ago
A few years ago, while I was still in high school, I began learning how to create websites purely for fun. One thing I found to be tedious was self-hosting fonts, with existing solutions to improve it completely abandoned. Consequently, I d
53.
by ayuhito 3y ago
Having too many options leads to a lot of bikeshedding as the whole ecosystem ends up fragmenting and disagreeing with each other. It’s one of things I really dislike about JS compared to something like Go. Personally, I stick to opinionate