Someone called out my code and technology choices in a public slack channel. They’ve clearly not understood what the code is doing (and it’s some of my clearest).
That’s not important though. What is important when you have a gripe with another’s shit:
- Read it again, harder.
- Speak to the author in private. Ask for their help to understand what’s going on and why.
- If you can’t speak to them directly, speak with someone else who can help *in private*.
It is proven! I am qubyte on Keybase: https://keybase.io/qubyte/sigchain#0b5f447fb0abc2d9db6abe09436a188e5e48ed616577b845a88a6370f64070ae0f
Those orchestral bits in Hear Me put me into a coding flow. I've not achieved a flow in months, and I've got a massive grin on my face now. #empath
I seem to end up listening to the demos of Devin's albums more than the regular tracks. #empath
I should have tagged this with #empath
Please sign. Revoke Article 50 and remain in the EU. https://petition.parliament.uk/petitions/241584
Please #StopUsingMedium. It’s really annoying and makes me not read your content, no matter how good it is. Not specific for this author. This a general statement.
I recently made a small contribution to Node.js.
Server side (mainly) web + game programmer and one time Quantum Information Scientist.
Server run by the main developers of the project It is not focused on any particular niche interest - everyone is welcome as long as you follow our code of conduct!