soft_dev_person

17 ms·

151.
by soft_dev_person 11y ago
Changes in the specs requires negotiation anyway if you have a contract with an upper time/cost value. Charging by the hour doesn't solve that, unless you have a no limit contract that puts more or less all the risk on the client.
152.
by soft_dev_person 11y ago
> No one is paying you for your “time,” they are paying you for a result, so stop charging for your “time.” I wish regular employers would adopt this more as well. My value is what I do/produce, not how much time I spent doing it. S
153.
by soft_dev_person 11y ago
It's asymmetric encryption. Even if the server got a hold of the public key, it would not be able to decrypt the contents. How to ensure the server doesn't get a hold of the private key is the issue (can you really trust the code
154.
by soft_dev_person 12y ago
This looks really nice. Subscribed! So, how many new subscriptions have you got so far after HN caught this? Edit: That wasn't an accusation of cynicism, just curious.
155.
by soft_dev_person 12y ago
There's the ideal world, and the real world. The real world does not always allow you to follow best practices (or even good practices). Sad but true.
156.
by soft_dev_person 12y ago
Until someone starts to take advantage, and fills it with false reviews faster than the system can cope...
157.
by soft_dev_person 12y ago
I can agree with most of this, and can relate in a recent discussion with some hired developers regarding use of tabs/spaces, indentation and code review. They were definitely in the "GSD"-camp, where the output is all that m