5 ms·
Clearly the guy didn't have to pull out a working PoC in one week with a forced uppon JS framework that just changed its public API and not its doc and that nee
by sametmax 7y ago
Clearly the guy didn't have to pull out a working PoC in one week with a forced uppon JS framework that just changed its public API and not its doc and that need magic lines just for webpack to not crash.
Or that has to pull data from a manually written csv our client uploads at 3 pm on their managed ftp and an untested REST api designed last month by a one man start up, using a legacy client lib that only god and a fired engineer knew how to get to work.
Or that has to be done with a trainee designer that knows photoshop but will "learn this css thing on the way" , a remote turkish consulting firm and your boss dog barking next to you because animals are good for moral and we are agile right ?
Those theories are good in a lab while writting carefully crafted c for the board you designed the spec for.
- retiredcoder 7y agoTrue, I am big fan of them but there are some legitimate cases where a debugger is so practical. There is a lot of code out there that has very little logical sense per se other than elusive business requirements..
- Tade0 7y agoThis says much more about the work environment front-end developers are subjected to than anything else.
- sametmax 7y agoOr work with a geographer client that wants to integrate his first terrible, terrible plugin into postgis. Or contribute to a mess of an open source project that your microservice happen to depend on. Or debug your student exercice that found yet a brand new way to crash that you never heard of. Or find what are the side effects of your 3am emergency fix during the last red teaming. Programming is a vast land.