Hi! I'm Ambika and I develop software.
• Professional OCaml developer
• I love working on software that will be built upon by other developers
• In addition to OCaml, I enjoy writing F#, Rust, and occasionally Haskell
https://t.co/0lDTmiCSnR
3. Should every major open source project have a discord, slack, or some sort of IM community space for quick questions about architecture and the like?
Obviously a major benefit of the workplace is that you can expect a level of quality from your coworkers, but still?
My onboarding at AWS/EC2 would've taken a LOT longer if I didn't have people available to me who I could
1. Ask for a rundown of the packages we own, what they do and where changes will probably go
2. Ask for pointers to old commits and code reviews that add new functionality
This makes me wonder
1. Could the aforementioned "rundown" be materialized into documentation for e.g. open source projects? Would that lower the contribution barrier?
2. Would it be useful to maintain a document with links to old PRs labelled by what kind of change they make?
I used to teach Haskell by explaining the difference between the $ and . operators.
It took me several years to learn that the correct way to teach Haskell is to never mention $ at all 🙅♀️
These two operators just confuse the hell out of people.
Lots of folks criticise this analogy of static vs. dynamic typing.
I was looking for a real-world analogy but haven't found a better one.
I guess it's time to ask tech Twitter for help!
What would be a great analogy?
@paul_snively One year since I last bothered trying to find out😄 I've been away from the community for a while, I noticed more commotion recently and wondered if this might have been something that's changed in my absence