pratikdeoghare

This is what I did recently.

- I wanted it to implement 5 buttons for some actions. I told Claude only about 4 of them. Then I implemented frontend/backend for the fifth one myself pretending that I just joined the project.

- I made Claude implement backend only and frontend only and then connected them myself.

I will never ship without looking. I might not look right away and ship when I am pushed. But then I will go into the code later and look anyway.

I don’t care which way the industry goes. I like looking under the hood and understanding stuff. Understanding makes you much faster because you can think inside of your head. Because I understood the code I knew just what to do when something was off. I love it when that happens.

I do feel bad when I think I don’t understand. I still go back and read high school book even though my grades were good.

It might help to point out to students that not all things called “number” in math are for counting/measuring.

Even before complex numbers, I was confused by negative numbers. Why negative times negative suddenly positive?

I spent time figuring that out. When complex numbers came I was ready. I knew they were not really numbers that would count something. And that they are just called numbers.

> what do I do?

Very hard question.

Your work makes you one of the very few people who really understands the problem and solution and its significance.

If I understand correctly, you mean something like this.

#foo`fmt.Println("Hello world!")`

instead of current

#foo{`fmt.Println("Hello world!")`} .

This would mean code can have tags too just like bags. Right now only bags can have tags and children. If you want to tag something, you have to put it in a bag. This works for tagging blogs, code, other bags.

I think the extra braces are worth suffering for uniformity like the trailing commas.

I think brashtag is more effective than markdown at killing those things.

Because it stops after making you a tree. Markdown takes your document all the way to html. Making it do anything else requires much work.

file.md -> markdown -> file.html

file.bt -> brashtag -> tree -> to-html -> file.html

file.bt -> brashtag -> tree -> todo-list-maker -> todo list

...

file.bt -> brashtag -> tree -> ... -> ...

Brashtag is not about code at all. Most text is already a valid brashtag. It is optimized for human writing. For example, this comment is a valid brashtag document if you surround it with #{} which can be done by a program easily.

> It is a competitor to JSON. Not sure what brashtag does that JSON does not. I'm not at all convinced that brashtag is simpler than JSON.

As you have noticed it is poor substitute for json. It would be cumbersome to write config file in brashtag.

> This isn't a competitor to markdown.

You can write blog post in markdown. You can write it just as elegantly in brashtag. Only brashtag does not convert the doc to html for you. It just gives you tree. You write a program that processes the tree and produces html.

Example,

Markdown: # Lorem ipsum dolor sit amet

Consectetur _adipiscing_ elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam.

---

Brashtag:

#h1{Lorem ipsum dolor sit amet}

Consectetur #u{adipiscing} elit, sed do eiusmod tempor incididunt #b{ut labore et dolore} magna aliqua. Ut enim ad minim veniam.

OR you could write

#really big title{Lorem ipsum dolor sit amet}

Consectetur #super duper underline{adipiscing} elit, sed do eiusmod tempor incididunt #emphsize{ut labore et dolore} magna aliqua. Ut enim ad minim veniam.

I wanted to keep the famaliar things. We write code blocks with backticks in markdown and slack and everywhere so I used those. In fact I used $ signs earliar then switched to backticks.

> 'this is a bag named code with a blob, therefore it is code."

This would make #code{} a special bag. Right now no bag is special. Also it would be hard to find the closing } if somebody wrote unbalanced paren code in the bag like #code{ func main() { }.

What if you wanted say footnotes? html does not have it.

Imagine you could just say #footnote{This will become footnote} and have a little program that would produce html that will show it at the bottom of the page.

Shut up and learn Common Lisp using Practical Common Lisp.

This would be my advice. Why? My own road was haphazard. Other books broaden your mind and teach you really cool tricks. This book gets you using lisp like you would say golang. But it still teaches you the lisp things and broadens your mind. Time spent choosing will be better spent reading this book. After that PAIP, On Lisp, SICP etc.