Home

hardware asm c

https://learncodethehardway.org/c/ https://en.wikipedia.org/wiki/The_C_Programming_Language https://github.com/eholk/PrimitiveComputing https://news.quelsolaar.com/ https://www.yodaiken.com/ https://gankra.github.io/blah/text-hates-you/

c# erl(n2o)

js http://tiarkrompf.github.io/notes/?/smooth-tree-animation/aside13

sml

formality/Peter Landin/Carry Howard correspondence/Liner types and linear logic of Girar/Propositions as types

concepts software engineering

mtdv

I want to have a list of conventions forming some guidelines, and a set of automated checks to verify those conventions are not broken

Best practices, architecture, [anti]patterns

Modern code must live comfortably with legacy one and both are evolving

Continuously delivery - ideally each day

Clean code base, data flow, minimalism.

No black magic, inheritance, implicit behavior (middleware, attributes, weak connections), monads, dups, dependencies, implicit dependencies/events/checks/triggers

Bugs alerting, finally

prove system correctness. Strong types and tests

https://plantuml.com/ru/

https://www.planttext.com/

Infrastructure map (how data flows through services/servers/network and how it scales)

Architectural layers map (what subsystems you have for storing/transforming data)

Bounded contexts (how your logical services are split and mapped to architecture)

Main use cases dataflows (CRUD operations, data streaming/pushes, auth, payments)

Limit the number of patterns used for similar use cases

Limit the number of cross-context dependencies

Tests for main/critical use cases (ideally integration tests - starting from UI interactions)

document all different ways you can add a new feature.

limit the number of ways you can do that.

Ideally - having as few options as possible, every feature should be similar technically to others. https://github.com/Shopify/packwerk https://www.youtube.com/watch?v=6m4XPje76WU https://www.youtube.com/watch?v=_Kex5hwGE-w