19
points
nivertech
Joined 1,923 karma
[ my public key: https://keybase.io/nivertech; my proof: https://keybase.io/nivertech/sigs/TSPizHrahhxd9Q1ZrIOFu3_73baE_0_XgUQTWapr4Zs ]
- Distributed Systems
- DDD / CQRS / Event Sourcing
- Erlang/OTP, Elixir/Phoenix/Absinthe/LiveView, Elm
- kdb+/q
- GraphQL, MQTT, Pub/Sub, WebSockets, Long Polling, etc.
- PostgreSQL, Redis, DynamoDB, Riak
- AWS / GCP
- GPU Computing (OpenCL, CUDA)
- Agent-based Modeling/Simulations (ABM), NetLogo- I agree that time isn’t an input in the economic system.
Although, one can use either discrete or continuous time to simulate a complex economic system.
Only simple closed form models take time as in input, e.g. compounded interest or Black-Scholes.
Also, there are wide range of hourly rates/salaries, and not everyone compensated by time, some by cost-and-materials, others by value or performance (with or without risking their own funds/resources).
There are large scale agent-based model (ABM) simulations of the US economy, where you have an agent for every household and every firm.
- I use symbolic links, and Claude Code often gets confused, requiring several iterations to understand that the CLAUDE.md file is actually a symbolic link to AGENTS.md, and that these are not two different, duplicate files
The recommended approach has the advantage of separating information specific to Claude Code, but I think that in the long run, Anthropic will have to adopt the AGENTS.md format
Also, when using separate files, memories will be written to CLAUDE.md, and periodic triaging will be required: deciding what to leave there and what to move to AGENTS.md
- OK, but I think it's not up to the programming language designers to define mathematical properties of the operations on specific data types.
I think the most pragmatic solution is to have 2 tiers:
1. use existing standards (i.e. IEEE 754 for FP, de-facto standards for integers, like two's complement, Big-Endian, etc.)
2. fast, native format per each compute device, using different sub-types so you will not be able to mix them in the same expression
- Correct, but that's not how I think about systems.
Most problems stem from poor PL semantics[1] and badly designed stdlibs/APIs.
For exogenous errors, Let It Crash, and let the layer above deal with it, i.e., Erlang/OTP-style.
For endogenous errors, simply use control flow based on return values/types (or algebraic type systems with exhaustive type checking). For simple cases, something like Railway Oriented Programming.
---
1. division by zero in Julia:
julia> 1 / 0 Inf julia> 0 / 0 NaN julia> -1 / 0 -Inf - aka "loss leader" or "supporting the ecosystem"
e.g. VCs invest in startups commercializing open-source foundational/infrastructure projects not only for the financial RoI, but also because it helps their portfolio companies succeed faster while maintaining a smaller headcount or spending less on non-core R&D.
- Full-time cofounder(s) should have the right to fire other cofounders, at least until a formal board of directors is established
The problems start when you fire someone with equity closer to the cliff
Anyway, I don't get the original post, IMO an MBA is not the kind of degree that is worthy of delaying founding a startup
Best practice is to set a long expiration date, such as 1-2 years. There are different regulations about it in different states. After that unused credits can be accounted as breakage revenue.
If a company treats credits as money, it will have to comply with numerous financial regulations. For example, if a company compensates for SLA breaches with cash rather than credits, this could be considered insurance.