Why?
782 karma · joined December 21, 2017
[ my public key: https://keybase.io/klntsky; my proof: https://keybase.io/klntsky/sigs/pwxXenfw5vIua6K51hS4J46QAGacayuKJNiz5azvHl0 ]
Why?
Location: Tbilisi/Georgia
Remote: Yes
Willing to relocate: Yes, US
Technologies: Rust, PureScript, Haskell, JavaScript, EVM tooling
Résumé/CV: https://klntsky.dev/klntsky-cv.pdf
Email: my username at google's mail service Location: Tbilisi/Georgia
Remote: Yes
Willing to relocate: Yes
Technologies: Rust, PureScript, Haskell, JavaScript, EVM tooling
Résumé/CV: https://klntsky.dev/klntsky-cv.pdf
Email: my username at google's mail service
Both contract-based and full time agreements are possible.I don't want to think about HTTPS, my websites are low risk, mostly static pages (and there are tens of them).
Remote: Yes
Willing to relocate: Yes (US)
Technologies: Haskell, PureScript, Rust, Python, web stack
CV: https://klntsky.dev/klntsky-cv.pdf
Email: my username at google's mail service
---
I'm looking for a long term commitment as a SWE, preferably as a tech lead. My professional experience is mostly functional programming. Areas of interest:
- consensus research, MEV, privacy tech
- LLM tooling, use of LLMs for software development
People often implement error handling using constructs like regexp matching on status codes, while with domain-specified errors it would be obvious what exactly is the range of possible errors.
Moreover, when people do implement domain errors, they just have to write more code to handle two nested levels of branching.
Look up a chatgpt prompt for nitpicking or write your own.
So, nothing serious
https://chatgpt.com/share/67538beb-73e8-800a-b602-fe26b131e5...
HMU if interested in building it
It's a better app than it used to be, overall.