Viewing profile — saltedmd5

The power of DVCS is in that each developer who clones a repository has a fully-functioning local repository complete with history, which can be committed to freely and seamlessly …

You are wrong. GitHub is a hosting platform for git repositories, which has collaboration tools (such as issue tracking and code review) built into it.

In the context of the original post, he is referring to origin (the convention for a default remote repository), not master (the convention for a default branch).

I hope this comment is ironic. Great code should be predictable, obvious and easy to change.

This is why vertically-sliced product teams work - they minimise the communication and coordination overhead associated with Doing a Thing(TM), while layered or function-specific t…

Yes, but it is also supposed to communicate the point. Which is not always possible in a tl;dr because if it was the author probably would have just written a single paragraph in t…

AFAIK rebase always rewrites history. If you rebase your feature branch, you have at least rewritten the history of the local branch even if you then delete it and push to a new re…

Rebase is not simpler in any context - rebase rewrites history, which, if branches have been pushed to remotes, then necessitates force pushes, which in turn breaks any other insta…

"I try to keep my git workflow simple," and yet I see 'git rebase' but no 'git merge' in that list.

I think this is probably the most self-indulgent thing I've ever read.

The point is that returning an Optional gives you nothing above returning a null - in fact it increases complexity and makes calling code more error-prone for no gain. If your cont…

Thank you for calling this out. I have to fight this fight way too often. Optional is really for functional code, not for "eliminating NPEs," because it doesn't do that - in fact i…

Something isn't ironic just because you wouldn't expect it, something is ironic because it is the inverse of expectations. Like if her name had been Lady Smallheart.

> For simple sites, probably faster to just implement it than find a library and read the docs. Not really - the implementation flow for tools that do this sort of thing are typica…

Refrains from pointing out misuse of the term "DevOps".

This gave me palpitations and then killed my browser.

The problem is the idea that "layers" and "abstraction" come as a package. You don't need layers to create meaningful and useful abstraction - in fact more often than not they proh…

The truth is that the construction of CRUD web UIs _is_ 90% automated. The web and storage frameworks do the vast majority of the heavy lifting - the application code is really jus…

> That being said I think there is a minimum level of effort, intelligence, and resilience required to take advantage of certain lucky opportunities if they present themselves. Luc…

Actually, I think your comment is a simplification: there absolutely is a trade-off between money and satisfaction. That doesn't mean you have to become a starving artist to increa…

Re: first paragraph - incorrect. The problem with "specs" is that you don't know whether they solve the problem until the solution is implemented and shipped. And even then, you ha…

Thing is, the need to formally define "behaviour" like that is a symptom of poor organisational/team structure. If you have multi-discipline teams with end-to-end accountability fo…

Your job as a software developer is to solve problems with code - not to take the thing someone else designed and make it go. That line of thinking just doesn't work. Designing and…

"But software is the spec." This whole discussion can be replaced with this sentence.