>. For the geekiest of us: by default, this uses simple text search, but in Preferences, tab “Interface”, you can also set the search entry to use the Glob or Regular Expression syntaxes!
You don't find this kind of language in Photoshop documentation
"What does this teach us? Well, it teaches me to do more diverse tests when doing destructive operations. It also should probably teach something to Vimeo and to my contractor but I doubt it will (and yes, the upload for some reason is still manual to this day. Go figure!)"
So you wrote bad code, didn't test it properly, ran it on production on the Friday before a release and are blaming Vimeo and [name redacted]?
And your resolution was yet another cobbled together script that you probably didn't test?
This isn't a great article to have attached your name to
I'd hire this guy if only being for this frank about his mistake. He owned it and that is what I would look for.
After deletion, what should he have done? Postpone the go-live? That's often not a a cost-effective option. As for a risk-analysis the worst what could happen was deletion of the remaining videos. I don't think that that makes big difference in this situation. And to do the right thing, you have to have the infrastructure in place, if you are in a hurry. I doubt that's the case for a 10 heads shop.
Agree 100%. Acknowledged mistake, moved forward to find a solution. Reflected on lessons learned. Shared valuable lesson.
To me this indicates intelligence, competence, integrity, grit and generosity.
TechnicL proficiency is much easier to come by than integrity, grit and generosity. I would trust the author to deliver on commitments.
Aye, this is how you learn and make sure it doesn't happen again.
I did a similar thing ~20 years ago when I first started my career, accidentally deleting a production database because I thought I was working on the test database.
I owned it, learned lessons from it, and it's never happened again.
I'm sorry if it came off like that. The mistake in this case was completely mine (bad code and bad testing). The detour on the other two companies was mostly because this way of deleting/recovering stuff should've probably been avoided in the first place, other than that I'm absolutely not blaming anyone else!
Don't worry about all that - there isn't a developer worth their salt that hasn't made a mistake.
But I'd consider having this blog post and HN post retracted purely for future internet checks. It isn't a reflection on you, and your honesty is fantastic. But there is a lot to be said about using a pseudonym when it comes this close to your employers
"Recently, I was asked if I was going to fire an employee who made a mistake that cost the company $600,000. No, I replied, I just spent $600,000 training him. Why would I want somebody to hire his experience?"
Vimeo completed a major migration of videos between accounts with no confirmation or communication before commiting it, then refused to reverse the change. Hardly the best service.
The article hardly comes across as 'blaming' them for the core issue but they were definitely not helpful.
Earlier in the article, the author does call out that it's bad code, so he's not entirely blaming these companies. Anyway: You should not be afraid of thinking about what each party could have done better. Not just yourself, but other people too. When I look back on times where I only blamed myself for prod issues, it was less of a learning experience, and more focused on beating myself up for no good reason. That approach shows that I'm afraid of the consequences, and it's an effective way to feel isolated from the team instead of improving.
(Since the OP redacted the company name from the post, I've done the same in your comment here. I hope that's ok.)
(We do this sort of thing to protect users, usually as the result of an emailed request, and you can tell when we've done it because of the word 'redacted' in square brackets.)
"Prioritising the longevity of data can sacrifice the authenticity of what it tries to capture and preserve. When I say authenticity, I refer to how accurate and detailed the data in question preserves a particular state. An original raw image, for example, will capture a landscape much more authentically than written text would. Written text will inevitably comprise of ambiguity and even bias, if not distortion."
There's a reason why it's said that a picture is worth a thousand words. There are trade-offs, and at the end of the day some things are more efficiently described in text, and some visually.
Well, Facebook do use accelerometer for 360 panorama view.
Could be as simple and they initialise coroMotion when the app becomes active in order to have their render react without a new initialisation each time?
"So we’re supposed to be writing a game, right? But in order to make progress, we have to fix a bug. And in order to fix the bug, we have to write a test. And in order to write a test, we have to write a test framework. And in order to write a test framework, we have to understand a thing or two about macros."
You could just fix the bug?
Game development is a different architecture to 'regular' system development (especially if it is a solo project).
If you are testing to ensure the bug isn't reintroduced then you haven't fixed the bug.
Seems to use the EXIF data to display the image, so if uploading an image from a portait image you might want to strip that or it breaks.
Its pretty cool, but one thing that always bugs me - why is the demo page so bad?
For the majority of people, this is the only way they are going to see this thing working - would it really have hurt to have had an actual frontend dev nock something together for this? It takes away from the great work behind the scenes imho
>. For the geekiest of us: by default, this uses simple text search, but in Preferences, tab “Interface”, you can also set the search entry to use the Glob or Regular Expression syntaxes!
You don't find this kind of language in Photoshop documentation