cromo / cr Goto Github PK

“Find a job you enjoy doing, and you will never have to work a day in your life.” --Mark Twain

https://medium.com/the-post-grad-survival-guide/if-you-love-what-you-do-youll-never-work-a-day-in-your-life-i-think-otherwise-c54e719dfa9a

The person that cares least in a relationship has the most power.

You wouldn't launch a project without documentation would you? I wouldn't consider a product finished without at least rudimentary documentation, but I've seen many projects ship with few to no tests.

This would be an example of the simplest possible way to set up a WebRTC connection between two endpoints without any P2P data exchange. Why? After searching around for tutorials, everyone wants to build Skype clones, but all I want to do is get a UDP connection that I can send some data over. Many of the tutorials I've found use some library or third party service to help with setting up the connections, or spend half the tutorial setting up a server and websockets before getting to the interesting content. Furthermore, nothing seems to explain the flow to follow to get WebRTC working from first principles (given some API documentation), so some diagrams explaining the connection flow would be helpful.

While working, I came across someone who would rather not centralize abstractions needed throughout the code, meaning that there can be duplicates and that the call sites now need to know the specifics of abstracting things like stage or what query to use for dynamic thing groups.

While there are arguments to be made for over-abstraction (which I'm against, I also worked with an overengineer) - this helps reduce code complexity elsewhere and guides developers to use the API in a way that makes sense for our application. Not having it written down in code somewhere means "The abstraction is in my head, and it doesn't need to be written down for other people to understand."

Things like how to attach an IAM Role to an instance, the ways the functions are used and referenced (in that it appears that !Ref Thing appears to be the same as Ref: Thing and why you might use one over the other), creating routes and route tables and associating them.

After working on cromo/dias and running into issues that I didn't know how to diagnose when bringing in new modules.