Comments URL: https://news.ycombinator.com/item?id=28788668

Points: 1

# Comments: 1

And there's probably a typo in your FAQ, "We do not allow sexual of adult content or any kind."

The plan was that the browser vendors give developers deeper access so that they could test new elements/standards through web components and polyfills.

The AMP component library is one example of this, and stories are one of their forms. So basically if you use their tags to structure your content, it creates a ig/sc style Web Story.

The structure that they have is (3): Story -> Pages -> Layers -> Elements

Each page represents a tappable screen, Layers occupy the full screen, stack and have layout defaults like fill or lower-third and Elements can be regular html elements or other AMP components.

I think that it's a neat way of organizing pages of information and made a clojure wrapper around it here: https://github.com/rainbow-bamboo/sargam

1. https://amp.dev/about/mission-and-vision/ 2. https://github.com/extensibleweb/manifesto/blob/master/READM... 3. https://amp.dev/documentation/guides-and-tutorials/start/vis...

I was blown away by the scope of your work, and really appreciate it.

Personally, I've been trying to figure out a literate programming style for clojure, but when I saw that you had given up on it, I figured that if it was a barrier to entry for thi.ng contributions, then I might not stand a chance with my smaller projects.

1. Do you have any advice on building community around your projects?

2. Or thoughts on the more recent advances in literate programming like https://github.com/scicloj/notespace ?

Guide: "My conscience won’t let me call Ruby a computer language. That would imply that the language works primarily on the computer’s terms. That the language is designed to accommodate the computer, first and foremost. That therefore, we, the coders, are foreigners, seeking citizenship in the computer’s locale. It’s the computer’s language and we are translators for the world.

But what do you call the language when your brain begins to think in that language? When you start to use the language’s own words and colloquialisms to express yourself. Say, the computer can’t do that. How can it be the computer’s language? It is ours, we speak it natively!

We can no longer truthfully call it a computer language. It is coderspeak. It is the language of our thoughts."

SICP: "I'd like to welcome you to this course on computer science. Actually, that's a terrible way to start. Computer science is a terrible name for this business. First of all, it's not a science. It might be engineering or it might be art, but we'll actually see that computer so-called science actually has a lot in common with magic, and we'll see that in this course"

(https://ocw.mit.edu/courses/electrical-engineering-and-compu...)

I was just thinking that what we really want when we say "no-code" is the ability to think in terms of domain specific data structures instead of programming constructs.

## Re: Remembering effective rules When I'm documenting, often I'm in the mindset of, "I solved this problem today, and writing it down ensures that I won't have to re-solve it next month"

## Re: Minimizing decisions My most productive days revolve around making decisions up-front, ie planning out the steps of a project in a Kanban or bullet journal at a granularity of 30 min chunks (~15 min expected time, 15 min slack)

# Possibly Related Work ## Readme Driven Development https://tom.preston-werner.com/2010/08/23/readme-driven-deve... The idea is to write your readme before you start coding. Just enough upfront planning to imagine what the system will be, discuss with team, and make changes, while delaying making all the small decisions that are needed to actually bring it to life.

I think that RDD is an admission that small decisions exist, so we should try to make the best big decisions that we can up-front while the cost of change is lowest. Each of the small decisions that you make in coding adds friction to change.

## Basecamp Hill metaphor https://basecamp.com/features/hill-charts "The idea: work is like a hill Every piece of work has two phases. First there’s an uphill phase where you figure out your approach. You have a basic idea about the task, but you haven’t figured out what the solution is going to look like or how to solve all the unknowns.

Eventually you reach a point where there aren’t any more unsolved problems. That’s like standing at the top of the hill. You can see clearly all the way down the other side. Then the downhill phase is just about execution."

This too I feel is an admission that small decisions exist. It's an understanding that even when you have a plan, projects go through a phase in the beginning where there's a concentration of decisions that need to be made, and each of those decisions introduce some measure of uncertainty.

I found the smartphone app handy before the lockdowns, and I especially like how they handle emailing clients.

Just getting access to Clojure on Windows through a single graal executable saved me some heartache this week, and I can't wait to start packaging apps with it.

Kosmos might provide some inspiration or insight given that it's a open source visual editor for clojure.

https://kosmos.antonvolkoff.com/

https://github.com/jacobobryant/biff

But if it's just shapes, and I don't have to memorize as many new concepts, maybe the load will be light enough to be relaxing like Mini Metro.

1. Seek: If you give it a search term it'll display the results as list of links

2. Sort: Any links or images you click on while in Web goes into a list called the Stack. I think it acts like your working memory in the same way that a traditional window of tabs might, and the act of sending links to the stack may be related to the "seeking circuit".

Links in the stack can be clicked on to navigate to, or swiped right to be sent to the Store section.

3. Store: Links here are saved from the stack as you use the app, and you can create folders.

* https://imgur.com/gallery/AwBTxlZ Here's an imgur post I just made with screenshots of the walk-through and a gif of usage. I don't use it anymore because it's been unsupported for years so I'm assuming that it's not exactly secure, but I loved the idea.

It picks a card based on the recorded time on-press-up as well as the current accelerometer reading.

Demo: https://imgur.com/gallery/1UTO0Fe

I've used it for many bugs while programming. I find that the little bit of insight/encouragement goes a long way.

Does that count?

Comments URL: https://news.ycombinator.com/item?id=24165577

Points: 2

# Comments: 0