Timeline for How to handle silly requirements?
Current License: CC BY-SA 3.0
7 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Mar 8, 2014 at 22:13 | vote | accept | Paulo Scardine | ||
| Mar 6, 2014 at 4:45 | history | tweeted | twitter.com/#!/StackFreelance/status/441434391328600064 | ||
| Mar 5, 2014 at 21:09 | comment | added | Peter MV | And never accept the project if you know in advance it's being built on something you find wrong. I did the same when stopped using library A in favor of library B. Now, no matter how good reasons a client may have for using library A, I either try to convince him why I switched to B or I don't accept the project. Money isn't worth getting bad reputation. | |
| Mar 5, 2014 at 20:54 | answer | added | Adam Davis | timeline score: 6 | |
| Mar 5, 2014 at 16:15 | review | First posts | |||
| Mar 25, 2014 at 10:14 | |||||
| Mar 5, 2014 at 16:14 | answer | added | Chris Cashwell | timeline score: 23 | |
| Mar 5, 2014 at 15:55 | history | asked | Paulo Scardine | CC BY-SA 3.0 |