I created a front page Show HN project CodingFont.com with low code
retool.com
retool.com
1. Make a Show HN intersecting coding with something uncommon
2. Write an article about how you got on front page with Show HN
3. Write an article about how you got on the front page twice
4. Write an article about how you got on the front page n+1 times
Personally I appreciate the fact that they made an effort to implement some of the suggested changes. And I think that in such situations, when making changes and even maybe being tired when doing it, it can easily happen that something breaks, regardless of whether you are developing with code or low-code or no-code.
For example, when I tried the tool/game, I did not yet see a way of hiding the font names and I was thinking about exactly the fact that I may be biased towards preferring the JetBrains font because I use it in CLion where I write most of my code, and that as a result I may be ranking it higher than I would if the name of it was not displayed to me.
Show HN: Coding Font – A game to find your favorite coding font - https://news.ycombinator.com/item?id=29010443 - Oct 2021 (215 comments)
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.
Missing B612 Mono (I prefer it to Jetbrains): B612 is an highly legible open source font family designed and tested to be used on aircraft cockpit screens.
In 2010, Airbus initiated a research collaboration with ENAC and Université de Toulouse III on a prospective study to define and validate an “Aeronautical Font”: the challenge was to improve the display of information on the cockpit screens, in particular in terms of legibility and comfort of reading, and to optimize the overall homogeneity of the cockpit. https://github.com/polarsys/b612
Previously on HN: https://news.ycombinator.com/item?id=18946601
re: Site presentation, I think having sample prose as well as sample code is important. Spacey code blocks are largely non-representative when it comes to typography in context. Particularly when working on the console with high density information (SQL, stringy datasets, etc.)
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.