Computer Science Student @ Georgia Tech. Former Intern @ Macy's Tech, PagerDuty, Uber, and Facebook.
Adopting a growth mindset is what allowed me to put myself in the right state of mind. It liberated me to ask questions without the fear of looking stupid. When you know that you are not…
…Corner is all about. To differentiate these remote APIs from the local system APIs mentioned above, I like using the term “Web API” now and then. (Although some people use that term for local APIs in the browser — confusing, right?)
Most designers don’t design things for people. They design solutions to their own problems (i.e. I want to make attractive things, I want to finish this project etc). When Don wrote DoET he was speaking about kettles, microwaves, and doors. But the same applies to User Interfaces, public transportation systems and the mega structures dotting our urban centers.
…eryone wants to do. I think we should celebrate refactoring as much as a product or feature launch. It’s important to celebrate the small wins alongside the big ones.
A lot of great software engineering boils down to a few characteristics: being humble and thoughtful; being a good listener; being a good partner; and importantly, being a good citizen. I value folks who step up to do the things not everyone wants to do. I think we should celebrate re…
A common alternative is REST+JSON over HTTP, which has been the blessed solution for server communication for a long time. However, although that stack is great for the browsers to talk to servers, it is inefficient for server-to-server communication, especially when we need to send a large number of requests. Without automatically generated stubs and boilerplate code, we will have to manually implement the s…
First of all, persistent data storage is about implementation details. Sharing data storage across services exposes the implementation details of one service to the entire system. If that service changes the format of the data, or adds caching layers, or switches to different ty…
le services, sometimes across… services that have to be changed and deployed at the same time in order to build a single feature. A distributed monolithic system is often much worse than a centralized monolithic system because of the complexity and cost of coordination of multiple services, sometimes across multiple teams.
In microservice architecture, multiple loosely coupled services work together. Each service focuses on a single purpose and has a high cohesion of related behaviors and data.
Implement our own volume control to avoid changing your global operating system volume.
