jeanettehead17's comments

jeanettehead17 | 9 years ago | on: How to Pick Your Battles on a Software Team

Author here. I like to say 'this way would be better because...' as much as possible. Providing a business case to back up your claim makes it less personal. Receiving feedback is never fun, but IMO it's easier to weather when there's a reason for that feedback being given that's more than someone else's opinion.

Also having coding guidelines/linters is important from transitioning the conversation from 'I think it should be this way' to 'our coding standards say it should be this way' and removing some ego from the conversation.

jeanettehead17 | 10 years ago | on: The Disadvantages of Single Page Applications (2014)

SPA applications frameworks and architecture are so young compared to server side rendering and still evolving.

Why do they exist? User expectations of the web are increasing and waiting for server responses from any action isn't really cutting it anymore.

Of course it's harder to maintain state and develop - the patterns haven't been clearly defined, and SPAs introduce two sources of state (client and server) which is a hard problem. It's the cost of the demanded user experience.

Angular ui router, ember data, react flux architecture are all examples of things that have just started evolving to address these kinds of issues. All of these are very new and being constantly iterated on and updated. Angular ui router does a good job of handling things like the back button and managing the state of your page. Ember data has really powerful client side data state management, and react flux architecture presents a much needed practice of how to control the flow of data between server calls and views. HyperMedia APIs are another evolving technology for maintaining more control between the client and the server.

jeanettehead17 | 11 years ago | on: Writing Code for Humans

I haven't found languages that let you be lazy (looking at you javascript) to be maintainable long term as a server, especially as a companion to a SPA. The complexity of maintaining a SPA is high enough as is. Having things like stronger typing and more enforced patterns on the server help keep it organized over time, where having looser more flexible patterns always leads to a spaghetti server. With a SPA, you really do need as organized of a server as possible.
page 1