marshmellman

9 ms·

61.
On Opportunistic Refactoring(jonmellman.com)
1 points by marshmellman 6y ago|0 comments
62.
by marshmellman 6y ago
Where I live (Seattle), a portion of the self-checkout lanes are also closed to coincide with the level of shoppers. I was told that this is because of labor unions - basically it guarantees work for the cashiers.
63.
by marshmellman 6y ago
Has anyone successfully migrated from MongoDB to a relational database like Postgres? My team used Mongo, but we have a classic relational use case. We’re being bit by application code joins, no cascade delete, sloppy schema changes.
64.
by marshmellman 7y ago
I believe browsers will close the socket, not keep it open and then discard the response. Browsers certainly have no way to terminate server execution.
65.
by marshmellman 7y ago
Another reason to cancel pending requests is that there’s no guarantee on the order the responses will resolve. So the UI might display autocomplete results from an earlier user input.
66.
by marshmellman 7y ago
Our PM would identify and prioritize customer requirements (so creating a foobar in the UI is P1, renaming it is P2, showing a loading spinner is P3, etc). Then our QA tester would “bug bash” and assign priority to bugs according to the req
67.
by marshmellman 7y ago
Glad you're working on this! I'm an experienced developer from a more traditional background - do you ever foresee the internship serving as a _mutual_ vetting process? I'd love to be able to experience a company from the ins
68.
by marshmellman 7y ago
Uh oh. Since folks are posting their own implementations, here’s mine, written as an exploratory exercise for Angular2: https://github.com/jonmellman/angular2-minesweeper https://jonmellman.com/mineswee
69.
by marshmellman 7y ago
An additional benefit of this approach is that your checklists now get code reviews, git hooks, history, etc. for free. I mention this because I worked at a company where checklists were typically simply added to a wiki and required separat