coherently

That software development as a JOB means working coherently with other people / teams.

My conclusion after struggling with this for a while is that the database is the truth, but it's also the only one that's coherently transactional.

There are too many things wrong with this comment for me to address any subset of them coherently...

But Java-the-language is Newspeak: if I can't coherently describe a solution in its syntax and semantics, I have to resort to worse solutions.

And the idea of reaching Mars in months instead of years is too positive to coherently express.

Type systems help verifying that a specified algebra functions coherently but they do not help in designing that algebra.

Or did he half-coherently narrate it to someone who then posted it for him?

The people who know what they're talking about say it once, coherently and concisely.

It's hard to coherently sum up the response to Chinese hacking, because it's as big a component of the public dialog as NSA spying is.

This is way above my head to answer your question coherently.

I think it really needs to be presented more coherently to look very convincing.

> And the idea of reaching Mars in months instead of years is too positive to coherently express.

"The people who know what they're talking about say it once, coherently and concisely." I thought that was pretty clear.

However you are also expected to identify cross-cutting problems, rally the right people, coherently frame your arguments, etc to move the "implementing solutions to technical problems" needle (even if you don't directly write a lot of that code).

While that paper makes a generally true statement, trying to do the most profitable optimizations in the most profitable way is what dead-ended gcc for many many years:) At some point, you have to step back from what you are doing and actually design and engineer optimizations coherently, not just "do this little thing and that little thing"