573 karma · joined December 5, 2014
CSS Tricks had built a coding font microsite. In May 2022, less than two months after CSS Tricks got bought, the CSS Tricks microsite was broken, and someone reported an issue on Github[1]. Chris, who would be in an advisory role according to the Digital Ocean announcement, answered quickly:
> I’m afraid I’m not sure what Digital Ocean plans to do with it. I would, of course, vote for it to be re-hosted right at coding-fonts.css-tricks.com — and would be happy to help put it on Digital Ocean App Platform as well!
It was clear that Chris as an advisor wasn’t given any real access to decision-makers at Digital Ocean to make any difference in such a simple matter. It was such a simple and easy matter to solve that a bystander came forward and hosted the microsite somewhere else, ironically on Netlify [2] — a competitor to Digital Ocean.
[1] Github Issue: https://github.com/CSS-Tricks/coding-fonts/issues/116
I got furious following this series of blog buyout by Digital Ocean and seeing them destroy it afterwards. I want to write down a record what they have done over the years and make them accountable for their unethical business practice even after they correct some of the things I pointed out directly. I am curious what others here think of what they did.
One of the paid feature that I really like is fluid PDF on mobile screen. Most PDF is not very readable on mobile screen, it needs pan and zoom. The fluid feature make the layout become more HTML-like and fluid, and adapt to mobile screen size. That is a feature to monetize. not rotating pages!
Also, the amount of time you can loan a book is also an deciding factor. I noticed openlibrary's lending period is in 1 hour, vs. most other libraries lend out ebook for 3 weeks. The shorter the loan period, the more on-demand it will feel. I may borrow a book for three weeks, but I will only read it for a few hours during these three weeks, so most of the time is wasted. If the moment I close the library app, the book is returned, then everyone's waiting time can be shorten to almost 0. Why don't all libraries do that?
It highly depends on the context. Are they 20-something single person working on a high-pay job, or someone older with a family to support and struggling? The response needs to be different.
My guiding principle of finding the balance is that if something I can teach within simple instructions, in a reasonable length to be consumed in an app, I don’t mind adding it in even it seems complicated. A good example is kerning, which is adjusting the space between letters. Kerning is considered advanced level design skill, but the principle is so easy - it is like pouring sand between letter gaps and the goal is to make each letter gap contain the same volume of sand. With this straightforward instructions, all of my user tester kern the logo the way I would have (I am a trained designer). So I added it in.
I want the app to make my users smarter, not dumb down the app in sacrifice of the quality of results.
Knowing vue.js, it took me about one or two days to get my first app running and I felt learned after the first app. After that, getting project off the ground is not a hurtle anymore and i can develop new ideas and learn along the way.
I think knowing vue.js (probably React too since I know they are similar) will contribute to flattening the learning curve for Retool. Mostly it is learning 1) set up the data source 2) find places to plug in the data using {{}} syntax
knowing these two things can get one very far.
I am not affiliated or paid by the tools I used. I start writing about them on my newsletter when I found it useful, and then that leads to this guest post on their blog.