1,687 karma · joined June 3, 2015
For example I was photographing a horse show last weekend, and I have around 3000 pictures and 30 participants.
I used to do that "by hand" with a SaaS, it would take me a full day. I did talk with them to get access to their existing API, but they kept saying they didn't have an API... Stupid.
Now instead, the "generating and uploading" galeries itself takes a single command, and I can use the spare time to sort pictures, be nicer to the customers and take more pictures :)
I use PHP and bash for all of my automation, and python for the UIs.
I'd say 75% of my dev work is hard deadlines.
- immoral projects I didn't want to work on
- personal life decisions (long leave) and boring project
- company closed
- couldn't stand being oncall and had a lot of pressure outside of the job, leading to fast and bad choices
- ah, and yes, Ar$eholes, I had those too, but only once out of 7 jobs.
A deadline is a clear moment in time when the feature is needed. There's a reason behind it. "We need to be ready for event X", "Next billing period is in a week".
Fixed deadlines allow you to negotiate the content of the feature, and make meaningful choices when it comes to the amount of details and edge cases to handle.
Otherwise how are you supposed to estimate something? I can make you the same feature in a week or in a month. It's going to be more polished in a month, of course, but I can squeeze it in a week if needed, with limitations.
Embrace deadlines, you will love them.
It's probably super nice for beginners, because it removes a ton of friction. But why force people?
Though I agree: I can't think of someone who _needs_ a $1000 smartphone.
Odds are, these glasses have that built-in. And it's going to be a lot better for your eyesight than staring at a screen 50cm away from your face.
Guetzli is nice, if you don't have too many images to recompress (quite slow): https://github.com/google/guetzli
Never been very good at planning, tho.
I would also love to be able to specify the WHERE just after the FROM but before the JOINs. And also after them: - the first one to filter the rows before joining - the second one to filter after joining
Anyway, complexity stays relevant, no matter what language you use. That's the real deal.
It was great, until it became terrible.
Nowadays I don't develop mobile apps anymore. Last time I checked, Xamarin Forms was half decent to build simple apps, but you have to be pretty flexible on the specs and the visual design.
Still, for data entry apps and other simple purposes, it can be fine.