JIT is the way out performance-wise while the boundaries of the VM are what provide portability and safety guarantees.
347 karma · joined August 15, 2022
JIT is the way out performance-wise while the boundaries of the VM are what provide portability and safety guarantees.
grpc and Thrift are mostly backend service interconnects in lieu of RESTful.
Capnproto is also awesome.
My problem is often perfectionism gets in the way of shipping where I'll spend too much time on minutia. At work, coworkers are more liberal in tech debt accumulation because there's a drive to ship maximum impact that can be quantified.
I saw a startup that was so tech debt-heavy that they couldn't move. They were stuck daily patching nasty code.
Engineers who don't care about code quality are like coworkers with messy desks that spill onto yours.
Commit messages are a summary of what's inside.
The description area is for the test plan to prove your code was tested and doesn't break things beyond automated lints and CI/CD testing.
For side projects, I use Rails 7 to get things going and replace components selectively with native extensions and separate processes.
It's all about productivity, especially when small, because performance is rarely an issue.
Monkeypatching is evil.
Rubocop custom cops to reign-in what's allowed in CI/CD.
This marketing "optimization" usually leads to cycle inefficiency and excessively deep pipelines, causing expensive pipeline stalls should a branch not be predicted correctly.
YAML, OpenSSL, and ASN.1 are what happen when every feature in the world is added.
At MAANGs, Rust is taking over and Go is waning. Go allows for quick productivity from 0 but it plateaus due to an unwillingness to add features. Rust has a Haskell/Nix/(fancy tool) problem but it has a good productivity curve that keeps going. Sometimes worse is better as UNIX people might recall.
Wise engineers don't add complexity or try to be too clever. Simple and small is elegant. Secure engineers don't have anything to prove and create maintainable code. OTOH, paycheck-driven engineers are incurious to try new things or promote software craftsmanship.
Lack of consistency can be enforced by code style linters. Let the linters be the Bad Guy(tm). Get agreement and buy-in on these beforehand.
Separate the people from the problems: give immediate, actionable, constructive feedback privately. Use frame taking to show how their actions come across and the concerns you have... for example, who supports this code when there's an P0?
Mentors are also needed. If possible, hire or advance an "old timer" in the space who can teach some new dogs new tricks.
Whitespace... I come from Ruby land where visual alignment, proper spacing, and terseness are valued. Too many comments and too much whitespace are a distraction, just like condensing too much. In general, very small functions, good semantic naming, DRY, and few levels of indentation make code more pleasurable to read than giant god functions with duplication or excessive line length. Code that runs together without functional visual separation doesn't make it clear what's prologue assertions and setup, main work, and epilogue return.
There's also some fun related work on ASCII art rendering.
This sort of thing is/will still be useful for low-cost displays. I'm sure we'll have Wifi-enabled e-ink displays on cereal boxes soon.
I'm sure this is what the Palm Handspring did.
Also, I think the sticker shock is there but it depends on the value it brings.
If it's well-justified to bring a major advantage, then it's acceptable. Otherwise it looks like MIC wasting $$$ on toys when there's unmet social and health needs that are desperately underfunded.
It's important to communicate and assure ACID and CAP properties. It'd be nice to have an "ORM" data layer that's say an extension of GraphQL that can specify what sort of guarantees the app wants.
Stress maybe? How's your Maslow's sleep, diet, exercise, and mood?
Also, consider that age comparing now with peak performance of say 15-20's is unfair. Give yourself a break.
Maybe a sabbatical is in order.
Chefs will be up in arms.
Total the costs of icy sidewalk slip and falls, lost economic activity, and excess deaths (QALY) over 10 years. Spend 1/4 of that on a series of underground passageways (un)like MIT.
It's interesting that in web paradigm dynamic languages and low-level systems languages, defensive programming assertions of invariants are widely dismissed. Validation and sanitizing of external input is often lacking and the source of many security issues.
The problem domain is that most programming languages and application frameworks do a piss-poor job of separating and managing business logic around data storage and data mutation. MVC doesn't go nearly far enough. OTOH, there are fancy enterprisy business rule transaction systems that are divorced from most platforms.
I think the key here is standardizing formal business rules in a portable "EBNF"/"markup" manner to be language and framework agnostic while not being laborious as COBOL-like Cucumber testing.
---
PS: Actually, I prefer the fork of Signal, Session, because it doesn't require the metadata binding to a phone number.
The one who gets this mostly right is Shopify. They're the "Stripe" of shopping carts.
And for heck's sake, automatically associate previous guest transactions with a new account when a user finally decides to take the plunge.
https://en.wikipedia.org/wiki/Solar-cell_efficiency
(The top is 47.1%)
Mandate EVs, and suddenly the industry will respond.
The status quo finances oppressive regimes, the Holocene extinction event, and climatic omnicide.