The formal verification subject is tricky.
The formal verification subject is tricky. For a lot of software (especially in the web startup world) it is often not possible to hire someone trained in formal methods to perform extensive checks/proofs on software which undergoes rapid change as the company pivots every couple of months. Functional programming alone doesn't give you any guarantees about safer or more correct software than any object oriented language unless you ruthlessly exploit its type-system. Even if you do, the specs have to exist upfront and they have to be correct and stable. One can make the case that isolating side effects and capsuling them in a controlled structure is "the right thing" to do, but that alone does not give you any formal verification of your program. From personal experience I can only say that whenever I brought up formal verification because of security/correctness concerns, I was immediately shut down by business, because it's simply too expensive for software that doesn't control life-critical systems.
Posted by amm on Feb 22, 2015, 3:42 PM
Tags
Related issues
- IMO it's a bit more nuanced than what the author portrays it as.
- In the UK Amazon have now raised the price of general shipping to be 2/3 the price of a months prime subscription.
- Credit where credit is due, critics claiming "[Apple device] is too expensive for something that just does [basic function]" have been pr...
- I like to buy music.
- Meet K-Claw.
- Fable is way too expensive for basic software stuff.
Raise real-world problems, find people facing the same issue, and discuss solutions.8,000 issues0 comments
pricing (SaaS)
IMO it's a bit more nuanced than what the author portrays it as.
In the UK Amazon have now raised the price of general shipping to be 2/3 the price of a months prime subscription.
Credit where credit is due, critics claiming "[Apple device] is too expensive for something that just does [basic function]" have been pr...
I like to buy music.
Meet K-Claw.
Fable is way too expensive for basic software stuff.
[Meta] Abnormal Codex usage/quota depletion and usage-accounting inconsistencies — cross-report tracker
[FEATURE] Passkey (WebAuthn) sign-in for Claude accounts, across every surface
The formal verification subject is tricky.
The formal verification subject is tricky. For a lot of software (especially in the web startup world) it is often not possible to hire someone trained in formal methods to perform extensive checks/proofs on software which undergoes rapid change as the company pivots every couple of months. Functional programming alone doesn't give you any guarantees about safer or more correct software than any object oriented language unless you ruthlessly exploit its type-system. Even if you do, the specs have to exist upfront and they have to be correct and stable. One can make the case that isolating side effects and capsuling them in a controlled structure is "the right thing" to do, but that alone does not give you any formal verification of your program. From personal experience I can only say that whenever I brought up formal verification because of security/correctness concerns, I was immediately shut down by business, because it's simply too expensive for software that doesn't control life-critical systems.
Comments (0)
No comments yet. Start the discussion.