Regular Programming

About Databases

Data has moved to a real database. Next, there may be brave attempts to add actual structure. Working with a real database is nice, as is not losing data, and being able to restore.Not everything is ephemeral, after all.Database service providers and cool stuff they do are discussed. The deal with Elastic is clarified. Finally, it is revealed where you should store your traces.It is actually probably fine.LinksMongoDBRethinkDBEctoEcto changesetsDatabase schemaOpenAPIAsh frameworkDjangoDjango REST frameworkX-Request-IDTransactionsWrite-ahead logpg_restorepg_dumpBigqueryLogical replicationFly.ioElectricSQLFlutterReact nativeCRDT:sPhoenix liveviewFireflyWebassemblySQLiteDuckDBClickhouseDeveloper voices podcastEpisode about ClickhousePlausible analyticsFathom analytics podcastPaul Jarvis - the "Company of One " guyJack EllisLaravelFathomElasticsearchMeilisearchLuceneCardinalityHoneycombOpenTelemetryNew relicHyperDXDatadogQuotesA worse MongoDBMigration completeEverything is ephemeralThe idea is to add lots of columnsIt seems a bit more DjangoThe stakes were high but the budget was almost zeroIt is actually probably fine

About Mingling

It seems a mingle is a thing, and not just in Swedish! But what do we want to get out of them, how do we go into them, and how do we create good ones?Do you want resonance or hole-poking when you tell people about your plan to arm toddlers with nuclear weapons? Do you want to successfully mingle nerds, or just hit the snacks hard?The foood, the cake, the coffee, and the old classmates. Too hot, too loud, too crowded.LinksMingle (noun)Ben OrensteinTupleThougtbot podcasts - The bike shed and Giant robots. Ben was on episode 183 of The bike shed and episode 136 of Giant robots.ØredevThe art of gatheringThe Whova appQuotesInteresting and funArm toddlers with nuclear weaponsWe don't trust solutionsExcitement and resonanceIntensively and excitedly and indefinitelyThe active rubberduck strategyTalking to fish in a barrellSuccessfully mingle nerdsHit the snacks pretty hard

About Performance

Performance: we wish the incentives were there to focus on it more often.Lars would like more opportunities and incentives to focus on making things fast, rather than just making them not slow. Unfortunately, things tend to line up so that fast enough and more features are in focus. Plus, performance and optimization can be very context sensitive and age out without anyone really noticing.Also pondered: IRC, Gentoo, and the eldritch horrors buried within the x86 architecture.LinksGrepos.walk() in PythonWhy GNU grep is fastRipgrepAg - the silver searcherTravelling salesman problemBin packingMnesiaORMProject EulerFibonacci numbersD. Richard Hipp - the guy behind SQLiteChangelog episodes with RichardXKCD and IRCIRCIRCCloudMatrix and ElementElmSVGCanvasNeovimLispArchNixGentooFuntooDartFlutterSkia - the graphics library under FlutterLinked listPointersCISC - Complex instruction set computerRISC - Reduced instruction set computerio_uringQuotesGiven up on old man ElixirGotta go fastI never really needed itGrep, naivelyAll the problems at the same timeTravelling knapsack problemMy ORM-infected brainMeasuring things and muttering under my breathI have a hobby, I do job interviewsTools by toolmakers for toolmakersI'm the IRC guyMachine-whispering optimization

About Developing Speed

CTOs want the ability to get prototypes built and out into production fast. Others preach the gospel of building things properly. How fast can you be? How much can you perpare before you hit the ice? And one you built and shipped that prototype, how can you get any kind of speed trying to maintain and evolve something where many corners were cut for speed?How do we want things to work then? Having an algebra for things might be nice. A sprinkling of interface, things that break noisily, and nice toolboxes to work with structs are all discussed.LinksThe Scott - Amundsen race to the South poleAccelerate, by Nicole ForsgrenParse, don't validateMnesiaDeep modulesPure functionsPlugElmBruce TateCRC - Create reduce convertEctoRocHappy Path Programming. Episode 47 features Richard Feldman and RocRichard Feldman, creator of RocQuotesThe gospel of building things properlyThe key to speed on the iceBefore you hit the iceBare mapsEvery step made senseThe original intent very easily gets lostThe curse of all softwareStrive for maintainabilityIt must not sprawlA little sprinkling of interfaceAt dawn, we roadmapThings that break noisilyA quantity unitlessThe simple case of HTTP

About System Design

Did they do design, or did they just do a system?Distributed systems are hard in many ways. Andreas describes a system communicating between backends and mobile phones in exciting ways with many exciting possibilities for errors. Like data format changes, loss of messages, having 1.5 source of truths, and of course ordering.In certain cases, nobody likes an optimist.The discussion then moves to discuss the working well-windows for various networking solutions, before diving into WebRTC and finishing up with the various dangers of auto.LinksRecursionEventual consistencyPubsubRethinkDBEvent sourcingReact nativeAndroid studioMnesia - a "distributed, soft real-time database management system" written in ErlangDirty reads and writesWebsocketsQUICUDPTCPWebRTCNATHTTP live streamingLars' ElixirConf talkZoom H4Zoom H4n proQuotesWorking with systems and feeling the pain Coping with system designEventually consistent, on a good dayEventually sourcedA disappointment to work withYour internal representation of the userThis is the shape of the data, deal with it1.5 source of thruthsOh, it's an optimistI don't like optimists at allOptimist databasesWithin its working well-windowOutside of the working well-windowA crash of serversBad connections over long distancesI don't do math