While users don’t think a whole lot about underlying software design, it’s an essential part of getting the customer experience right. Listen to our interview with Pete Fleming, Head of UX at Chariot Solutions.
The Representative State Transfer (REST) protocol has been the king of remote access protocols for web applications for well over a decade. The general pattern: expose “nouns” (Customers, Activities, Employees, Tasks, Sasquatches) as URLs (/api/sasquatch/32) and access them via HTTP “verbs” such as “GET”, “POST” (create), “PUT” (update), or “DELETE” (umm, well…). The content type is specified via HTTP headers such as Content-Type (for data being received by the client) and Accepts (for a data request). The reason this works…
I’ve been experimenting with Workspaces for a week now, and have configured an instance for aws re:Invent for those times I want to hack. Coupled with an iPad Air, a bluetooth mouse, and the keyboard case, I have desktop I can pull up anywhere.
Chariot’s AWS Practice Lead, Keith Gregory, recaps his experience at Amazon’s re:Invent conference in 2019.
If you weren’t able to attend our IoT on AWS one-day conference, here’s a recap.
Optimizing wireframes is worth the effort because it will save time in the long run, and better facilitate the implementation to meet the vision.
Given that hardcoding is a bad idea, how should you manage your AWS keys? AWS gives you three options, which we analyze in this post.
Joining a project after it has already started is no easy task, especially when the project is launching a complicated enterprise application with a short deadline.
My last post compared different infrastructure tools for creating users and letting them assume roles for cross-account access. I received a few questions about the underlying problem that those scripts were trying to solve, so this post delves a bit deeper into the realm of user management.
This post was written by Emily Melendez, a Software Consultant at Chariot Solutions.
