• Guess and check 1

  • Model – Solve a simpler problem. In chess you reduce a complex problem to a simple end game 2

  • If you can’t find a solution, try assuming that you have a solution and seeing what you can derive from that – work backward 3

  • Use symmetry 3

  • Use direct reasoning, Consider special cases 4

  • Eliminate possibilities 5

  • If you are having difficulty understanding a problem, try drawing a picture. If the problem is abstract, try examining a concrete example.

  • Try solving a more general problem first inventor’s paradox: the more ambitious plan may have more chances of success

  • Apply a similar heuristic

  • Be positive. Take help, learn from history. Some problems are intractable.
* Crystal
  • OOC
  • Elixir
  • V
  • C2
  • Zig
  • Julia
  • PicoLisp
  • Hakaru
  • D
  • Esterel

[eccentric languages]

[visual languages]

Really digging the concept of open startups.

The biggest win from open source is transparency. By having more data, especially with regards to raw materials and revenue flows – everyone gets to make better decisions. Employees get an idea of how much they make. Companies also get to share important pricing informations so that they can innovate further. If companies want to have limited liability and benefits, then it makes sense for governments to ask for 100% openness. Economy becomes transparent as demand and supply can be seen and it improves economic calculability.

Just remembered control theory from school which is like the meta theory of electronics. There are no types and things are mostly dealt from the perspective of stability, feedback, error rates … this could be an alternate footing to the foundations of programming – making control theory the main root of programming.

“Do not spoil what you have by desiring what you have not; remember that what you now have was once among the things you only hoped for.” ~ Epicurus

Biggest blocks

1. Mundane / Habitual work
2. Work requiring other peoples input
3. Perfectionism
4. Trying to impress others

Any complex tasks is a series of small tasks. Divide a complex task into simple tasks to get started.
Time and Energy are like budgets
45 – 90 mins max concentration after that you experience a burnout. Only work in short busts of productivity and mentally practice before working. Start day with todo
Divide work into longer timespan with small chunks everyday. Process > Goals
Parallelize around blockers
Batching – Combine boring tasks
Best ideas come in seconds or minutes. Let your brain work in the background. No way you can force it if it a serious problem
Bad ideas lead to good ideas. Give yourself permission to write garbage. Taste hinders you
Do other things … one thing can inspire another thing
Make it fun follow the fun. Think about beating your previous record
Think of the impact for motivation
Multiple rehearsals to get 1 final presentation right. A task needs to be done atleast 5 times to get it right – outline, draft, revision, feedback, final



Can everything be automated from raw materials to final product ?

This is how cars are manufactured today.

In software the replication cost is zero unlike hardware where you need thousands of people to assemble parts. Software is a discovery driven field unlike an assembly line, although managers insist on the assembly line. It seems with the release of Github Co-pilot we have entered a similar era in programming. Will retro programming be a thing in the future like retro car building ?

Assuming a robot can replace 10 people cost-effectively it will add 4 new jobs while taking away 10 jobs. The new 4 jobs would be

1. Supervising the robot
2. Hardware Maintenance / Repair
3. Programming
4. Data maintenance, AI maintenance

The jobs like marketing, management, accounting … will be similar to the jobs held in the previous technology. The training cost for teaching people familiar with the old technology, the new cool thing will be significant not to mention the environmental cost. Aesthetically speaking old technology has a charm but new technology is just too cheaper to ignore. Case in point, AWS with its dynamic IP address effectively replaced the hardware load balancer and created a new dev ops field as a result.

Telegraph – Telegram / Twitter
Magazines – Blogs
Radio – Podcasts
Gossip – Forums
Reviews – Comment Sections
Telephone – WhatsApp
Yellow Pages – Google / Amazon
TV, Home Videos – Youtube
Cinema – Netflix
News – Newsletters
Post – Email
Academic Journals – arxiv
Printing press – Documents
Telephone Orders – E-commerce
Phone networking – Crowd Funding, Event Management
Training Videos – Coursera

Communication requires a medium – oral, book, cinema, radio, tv, newspaper and magazines. Computers provide poor dpi, resolution, bitrates compared to analog. While previous mediums are 1-1 and 1-n, computers with internet enable m-n with sync and async modes. Bad quality content happens for large m and large n. When m is small and n is large, it resembles TV with all its faults of propagating uncritical mythos. Cost for consumption increases as m increases. Cost for creation increases as n increases.

Internet is an unregulated medium and it is content agnostic – text, images, video, sound. Like Pirate Radio, m and n can be small – this is the most unique possibility with the internet. Now internet is a new medium but academic publishing is old, they have an important connection though. It’s the hyperlink or the reference. Unlike all else, the property of this medium is permanent memory. All other mediums rely on people forgetting stuff, after the communication is over. In the internet not so much! You are expected to google and dig deep into the hyperlinks. In an academic journal, you are expected to read the footnotes. This makes internet communication one way to record and to preserve cat pictures, truth, facts and arguments although they can be easily distorted if we are not careful.

For consumers and creators the easy way to use internet is to treat it like an extension to tv, news, magazines, yellow pages and find niche communities. While there is negative employment for middlemen, computers provide new forms of employment – designers, programmers, hosting companies, crooks. For knowledge workers it provides new ways of dissemination – marketers, teachers, journalists, scientists and finally computers provide new venues and collaboration spaces for entertainers, hobbyists.
The app.
The literate source code written using wheel.

This is probably the first web app written using literate programming.


Odd to find almost no search results discussing this, while language chauvinism is well known and studied as an aberration.


LXD + ZFS = pure awesomeness

You get docker like capabilities and isolation but with the feel of using a normal dev environment. Easy snapshots makes taking backups a breeze.

The constant assumption is that C only supports procedural programming, however if we observe the C ecosystem it becomes clear that its really not the case.
Unix Supported Paradigms

1. Event driven programming
2. Asynchronous programming
3. Data Flow – pipes
4. Parallel programming – fork, threads
5. Exceptions – signals
6. Modular programming – dlopen, plugins via dlls
7. Message Oriented Programming – sockets

C Supported

1. Generic Programming – void* , preprocessor, varargs
2. Generative / Macro programming – preprocessor, lex-yacc, autogen, gsl, gpp, m4 which generate C code
3. Object oriented programming – custom vtables which favours composition over inheritance, also see this, gobject and enlightenment support mixins as well … not to mention other techniques like decision tables
4. Automata programming – gotos and arrays of labels, SMC
5. Stack programming ~ inline assembly
6. Functional programming – function pointers and libcello, tagged unions, coroutines

External Libraries

1. Actor model ~ zeromq + supervisor
2. Literate programming – noweb
3. Logic programming – Databases
4. Garbage collection – use gcc builtin defer and external garbage collector
5. Array programming – C memory model, numpy
6. Audio programming – LV2, openal, puredata
7. Graphics programming – opengl
8. Differential programming
9. Coroutines
10. STL

While C++, Java, Objective-C may claim to be descendants of C they really are more like PL/I and multics in spirit because of too much centralised planning and perfectionism; techniques which have persistently been shown to be disasters is software projects. Why C ? Well …

1. The other communities have shown a profound lack of integrity and sleazy sales tactics (snake oil, fud, us vs them, eee) in their marketing. The adoption was forced on programmers in a top down way by non-programmers and licenses than by voluntary adoption by teams or natural market competition. They also setup a false dichotomy and rhetorical gimmicks of high level vs low level, strong vs weak as opposed to broad vs narrow.
2. Other languages are complex, difficult to explain to beginners and encourage pedantic, patronising thinking. They also copy the worst traits of mathematics – namely abstraction for abstraction’s sake and bad naming conventions. Like physics, chemistry programming deals in concretions. Like electronics it is better for programming to be bottom up.
4. Other communities are obsessed with superficial and subjective arguments – code cleanliness, code purity as opposed to code reliability. They merely look modern, but they are not modern in the sense of empirical and science but aesthetics. None of the languages have come close to implementing a server like apache or the tcp/ip stack. The benchmarks compare apples to oranges in sweetness.
5. Completely failed predictions … 0 modern operating systems are written in C++ and Java. Their success lies in using XML based guis which you can also do in C. Blender is written in C.
6. Better programmer happiness. More hobbyists pick C than any other language. Large open source codebase.
7. Code longevity, portability and less API/ABI breakage
8. Mono-thinking cultures are simplistic and inherently less creative, less innovative while suffering from philosophical hammers.
9. C and programming languages written in C dominate the web, embedded space and performance metrics while others are slow. If you are looking for performant web servers checkout – lwan, kore, open resty, onion
10. Extremely rich tooling and cross platform support.

What can C programmers improve ?

1. Better naming conventions
2. Use garbage collection for non critical tasks
3. Use namespaces and nested functions
4. Better security with bounds checking and garbage collection

Biggest realisation today – flow is not a sustainable way to work.

Much like how exercise easily fatigues the muscles, too much focus or flow drains the working memory. It is critical to take breaks every 10 minutes to regain balance otherwise while the first day might be productive the next few days will not be.


If a task is already done the estimate is 0!

“I do consider assignment statements and pointer variables to be among computer science’s most valuable treasures” – Don Knuth

My biggest regret in my programming career is not sticking to just C. I should have avoided OO / FP and all the framework snake oil that promise to cure everything. If you are a beginning programmer don’t waste time in any of that, develop knowledge about applications, databases, operating systems and games. C + Lua should be enough.

To date C is the only language with which you can have a complete stack

1. OS
2. CLI / GUI Apps
3. Parsers
4. Games (all 8bit, 16bit games)
5. Embedded controllers
6. Networking

without a single line of any other language. Assembly too is wonderful! And because assembly instructions have a fixed format, it too is easy to parse – just like Lisp.

Myth – C can only be used in small teams.
Reality – Linux Kernel, FFmpeg …

Myth – C doesn’t have OO so it is not an “industrial” language.
Reality – C doesn’t force you to use objects for everything. You can do composition style OO trivially in C and there are multiple options to choose from. Blender, Gimp are complex GUI apps written in C not to mention Tk. C offers shared libraries aka modules which allows you to decompose teams along those lines.

Myth – C is not functional.
Reality – C has co-routines, const, pointers and function pointers which gives you all the advantages without abstract nonsense.

Myth – C is not secure.
Reality – Somewhat true. C programmers refuse mandatory bounds checking, secure libraries and gc but this can be fixed.

Happy with the progress of bitrhythm today! Glitches are still a pain though. Will add song save feature and an observers example call it day.


I have enabled webmentions in wordpress. Not sure how it is supposed to work. It seems to be the most useful feature.

Black and White thinking

This style of thinking is nothing short of delusional. The open source community has too much of this and too little pragmatism. The split between free software and open source happened because of this reason and we have been paying for it, ever since. Much like the creative commons community, FOSS could have settled on multiple styles of licenses.

Not anticipating tivo, cloud

Unix is a timesharing system used in routers everywhere. Not anticipating patents, tivo and cloud from the day one is nothing short of embarrassing.

Open Hardware

FOSS can not exist in isolation. Firefox and Ubuntu both failed in mobile. Corporations have successfully screwed over FOSS by locking them up in hardware; which is clearly anti competitive and monopolistic. Instead of having general hardware and consumer choice for software we have the opposite. The open source world has never really addressed this issue nor did it forge broader alliance with the open hardware and other open movements.

Open Source as a certification

Instead of having legal requirements for a business entity to call itself “open source” any corporation can pretend to be open source now, when they are in-fact mixed source. This is a drastic failure. No only could such a legal requirement be profitable for the certifying authority, it would also increase consumer visibility and trust. Now many consumers think they are buying open source when they are just using mixed source products.

PR disasters

Allowing the press to win the GNU / Linux naming battle which was a smear campaign in disguise. Also the usage of the word hacker in media. Being identified with communism and not with indie movement seen in music and elsewhere. The FSF has taken a half assed approach to this instead of using all legal measures to fight the press. No one really knows where FOSS stands. Every sane minded person should be vary of communism and M$ easily played on this fear in the 90s. On a side note, software is not a scarce commodity.

Appropriating funds and time for vanity projects and trifles like Firefox vs IceWeasel

The FSF has diverted more than enough funds on vanity projects like GNU Hurd. Early in the 1990s, Scheme was chosen as the language for scripting FSF projects on the insistence of Richard Stallman. Even now a number of major projects like GIMP are forced to use scheme. You can’t have compulsion and free in the same sentence. It is deeply hypocritical for FSF to dictate language choice just as it is immoral for a business entity to dictate how you should use your phone. The reasoning is here is nothing short of tyrannical. PHP has done more for free software than Lisp. The goal of FSF should be broader, safer choice in consumer software as opposed to any constraints and pointless forks. Customer support, user happiness, developer happiness, safety, transparency and ease of use are more important than crazy architectures and mere openness.

Why scheme ? Why not vala ?

Not building a business model around complements

This is also applicable for the *BSDs. Could FSF have funded itself by offering hosting solutions like digital ocean, selling books and hardware like Amazon, source management like gitlab and so on ? Instead of the D.I.Y attitude FOSS community relies on begging. Instead on yapping on and on about “free” and “open” software money could have the done all the talking. This is how profitable independent labels operate in the music world. Linux could have had an AppStore long ago with payment integrations, issue tracking and what not! Most open source projects don’t even collect email addresses of people who download and use their software. Only paid users getting priority ticket fixes could easily solve open source developer burnout.

Allowing redistribution and commercial use

The biggest achilles heel of open source is allowing redistribution of software as opposed to merely source available software available for private use. There are too many freeloaders on open source. It is also deeply unethical for someone else to make money out of your free contributions. Plenty of open source contributors are screwed over here when project owners get investor funding and contributors don’t see any of it. Github also did this cleverly by associating itself with words like open and community but never really had open source. This is nothing short of fraudulent. Open source developers need to understand contributor agreements before they commit a good chunk of time to work on open source. Money flows need to be transparent in open source.

April 2020 – April 2020


1. Quit smoking
2. Cut down on coffee
3. Invested in back support, neck support and wrist support
4. Using vitamin D supplements, L-Theamine for anxiety and detox
5. Exercise for 10 minutes everyday
6. Meditation
7. Quit twitter, netflix, HN, reddit, news after being addicted to them for 6 months of doom scrolling.

I guess I am finally old.


1. Nixos, Unikernels, Docker
2. CSS from scratch – tailwind, basscss, button shadows
3. vdom, svelte, pjax, websockets, caddy
4. ActorDB vs Rqlite vs Couchbase vs Custom Sqlite / JSON store
5. Wrote a blog engine in hylang, go, crystal, perl6
6. Moving away from google – WordPress, Goat Tracker, maddy mail server
7. Learnt a bit about Ethereum
8. Completed three projects

Also learnt more about mixing and remastered all my old songs.

Future improvement

1. Quit day dreaming
2. Better emotion management
3. Use RSS for everything
4. Reduce media consumption even more

More future learning

1. Elixir
2. Better writing
3. Cooking

Regrets – should have bought some Ethereum!

“People writing class will go to their graves not knowing how miserable they were”


ESLint github for lint configuration


1. Programming deals with perfection more than any other discipline, what is not perfect does not work
2. We are not paid to use every feature of the language, we are paid to write programs that work well and are free of errors
3. You should not take unnecessary risks to write code
4. Responsibility hierarchy … user > developer > manager
5. Time taken to type the code is not a good way to estimate. Time taken to make code work right can be very long

(Bad) Arguments against good parts

1. It is not a matter of opinion if there is economic cost in terms of errors and delays
2. Reduce my keystrokes is not a good argument (programming is not typing)
3. It is an insult to suggest that I would ever make a mistake (thats silly)
4. There is a good reason those features were added (nope)

New Good parts in ES6

1. Tailcalls
2. Ellipsis
3. Module
4. Let / Const
5. Destructuring
6. Weakmap
7. String literals
8. Regex literals

Bad Parts is ES6

1. Proxies ( I disagree)
2. Generators (I disagree)
3. Symbols
4. Iterators
5. Reflect
6. arrow functions (returns undefined)
7. class

Good Parts Reconsidered

8. Don’t use new
9. Don’t use Object.create
10. Don’t use this
11. Don’t use null
12. Don’t use falsiness
13. No for
14. Object.keys(object).foreach
15. Prototypes are bad. Memory conservation is a bad idea. Compilers can’t optimise.

“It takes a new generation to use good ideas”

I disagree with this part of the talk. Goto is a great idea when used with dispatch tables.

New proposals

1. class-free programming / functional inheritance with closures as an alternate to classes and prototypes.
2. Better number type – Dec64


1. Advices against types (you still have to test)
2. Actor based language could be the next
3. Web assembly makes javascript a systems language, probably not a good idea.
4. System testing over unit testing


Probably not a popular idea but one reason why the internet has turned to crap is unicode. I don’t think it makes sense to put everyone who speaks differently in the same bucket without creating a massive cross cultural storm and confusion. Communication pre-supposes language.
I have dropped twitter, google from my life from 2019. Facebook since 2014. After trying Masatdon for a bit, I have decided to embrace wordpress more fully. Slow, neutral, un-opinionated and more thoughtful media please. My brain has recovered from the constant hate fatigue, fear mongering and the bullshit senses are back.

What do social networks actually provide ?

  1. No hosting mess
  2. Simpler UI
  3. Discovery / Search
  4. Friend Feeds
  5. API
  6. Multiple media types
  7. Contact management

Mastadon can do 2, 3, 4, 6, 7. WordPress solves 1, 2, 5 and 6 but lets google do 3, email do 7 and RSS do 4. WordPress is IndieWeb. WordPress providing full text search across all its blogs and a friend feature could make it more like Mastadon.

Other indie web projects I am excited about,

  1. Owncast vs Twitch
  2. Peertube vs Youtube
  3. Lemmy vs Reddit
  4. Beaker p2p browser
P2P is better than federated. Federated still suffers from blacklist problem – whether it is email or mastodon. Federated is definitely better than blockchain. There’s also diaspora, signal, discourse, matrix, xmpp and IRC which are built on solid foundations. Reddit used to be open source but it is now closed. Perhaps individually seen IndieWeb seems small but WordPress  already powers a good chunk of the web. If you combine all the numbers and include forum software, static blogs as well, IndieWeb powers the majority of the web. Time to build a new p2p Google so that we can take discovery and search into our own hands!


compose new post
go to top
go to the next post or comment
go to the previous post or comment
toggle comment visibility
cancel edit post or comment