9 ms·
Apple Aperture: Senior QA (2004-2005)
- kissgyorgy 7y ago> Many people, including myself, developed long-term health problems. One person, as I mentioned, had a nervous breakdown, others just took forever to get any spark back in their careers. I would look these people in the eyes, and they had this look like someone close to them died. The same thing happened to me last year, and basically this is the reason I have been shadow-banned from HN. I stayed for 2.5 months only, but it was still too much, because I thought I got a decent salary. It cost me twice as much since then because I wasn't able to work since 4 months and I have no clear idea how I will crawl out this huge hole despite taking antidepressant, tranquillizer and going to psychotherapy every week. DON'T PUT A PRICE TAG ON YOUR MENTAL HEALTH, and get out of a terrible job until it's too late! It's not worth it, believe me!
- davedx 7y agoHang in there mate, it will get better. Humans are resilient. FWIW I see your posts fine.
- hu3 7y agoThanks for your strong but necessary words. I'll point a friend of mine to your comment. He's constantly complaining of work. Once a bright engineer. Now his eyes look soulless.
- eddieh 7y agoMy last job drove me to therapy too. It get's better.
- spiderfarmer 7y agoAs a former manager I always read these management failures and wonder how on earth these people ended up in their positions. To be fair, I hated being a manager but I enjoyed having a happy, confident and competent team. So maybe the job just attracts people who love drama.
- hhas01 7y agoAs a former manager (who sounds like a good one), are you able to shine any light on why management cultures appear so reluctant to eject malignant managers? Any bad employee will damage the business and those around them. But where a typical bottom-rung grunt has a very small scope of influence and is relatively easy to fire, even a mid-level manager has more than enough power to ruin entire departments; and once they’re c-suite the game is all but done.
- goatinaboat 7y agowhy management cultures appear so reluctant to eject malignant managers? A typical engineer will gladly stab another in the back for something so trivial as what nearly-identical-anyway programming language or framework or IDE to use. Meanwhile managers, like lawyers, accountants, doctors, teachers and every other profession, prioritise solidarity within the profession. We can debate whether that’s good or bad but there’s no doubt why they prosper while engineers are the first to be outsourced or exploited.
- Ididntdothis 7y agoVery true. I have noticed this too at my company. Other departments promote people more, hire faster, waste money on offsite fun meetings whereas engineering rarely promotes people and generally makes each other’s lives miserable. In the Gervais principle hierarchy I definitely feel we are the losers.
- briandear 7y ago> Meanwhile managers, like lawyers, accountants, doctors, teachers and every other profession, prioritise solidarity within the profession. Have you worked for any length of time in those fields? Don’t know if you ever worked as a lawyer but “solidarity” isn’t a core value.
- goatinaboat 7y agoDon’t know if you ever worked as a lawyer but “solidarity” isn’t a core value. Solidarity to the profession. They may squabble amongst themselves but they’ll never compromise the general prestige of lawyering. Nor tell the client that what they do is easy and anyone can learn it, even if that’s true.
- izacus 7y agoIs this kind of working environment normal at Apple? This isn't the first story I've heard about mandatory long hours and screaming in the office. Can anyone else chime in?
- ido 7y agoI have no idea about Apple specifically but I've heard similar tales about other large tech companies. It seems endemic to our industry for some reason (maybe its also endemic to other industries, but I wouldn't know).
- jfb 7y agoIt depends on the group. Apple's silos mean that individual directors and VPs have a lot of influence over the working cultures of their teams, and a lot of those leaders ape their management's style, which, when His Nibs was still a going concern, involved lots of screaming and abuse. So it could trickle down. I was lucky in that during both of my tours, my management was humane, but that's sort of the luck of the draw.
- grecy 7y agoReading that story made me feel sick. As a young Engineer my dream was to work at Apple, but I'm happy I never did. I don't understand why people tolerate that kind of treatment. Never in a million years would I work nights or weekends or allow anyone to scream in my face. That's just not life.
- Bahamut 7y agoThere’s a fair number of people who work weekends voluntarily - I’ve even gotten bug reports on odd days when corporate is shut down like Dec. 26th. My manager and some on my team at Apple generally discouraged me from working on weekends - I’ve worked some on weekends mainly to de-risk accomplishing certain tasks due to me being in an optimal state to tackle some issues & having some spare time. Occasionally I have to fix operations issues on weekends too, but those get resolved generally pretty quickly. All in all it’s a YMMV situation. Most people in my org keep to normal hours, have same development timelines, and are pretty happy (no yelling/screaming, most operate somewhere in the 10-4 time range give or take, 5 days a week).
- peteforde 7y agoThe strangest thing for me reading this is that, well, I loved Aperture. I used it loyally from v1 until long after it was EOL'd. I spent thousands of hours in it, and it really fit my ideal workflow. There was a lot of functionality/crap in there that I did not use, a lot of functionality was hidden away behind context menus and a lot of promised features around integration with plugins and 3rd party never really materialized, but in terms of core function it was a total workhorse. Apple ultimately went to great lengths to purge it from existence, even for those of us with paid licenses who'd been told (or at least safely presumed) that we'd be able to install it on new machines via the app store, even if it wasn't available for purchase. In reality, they removed the binary from the cache. At one point, I went through a ridiculously elaborate process of obtaining a certain kind of physical license from eBay and spent hours emailing random Apple employees - likely some of the folks mentioned in this story - getting them to make exceptions and pull favours to make it possible for me to install it one last time before Catalina pulled the rug out for good. Fuckin' Apple.
- Wowfunhappy 7y agoFyi there’s a process to get Aperture working on Catalina. Don’t have the link on hand, but if you need it I’d be happy to dig it up.
- peteforde 7y agoI would be very grateful.
- Wowfunhappy 7y agoHere you go! https://github.com/cormiertyshawn895/Retroactive https://github.com/cormiertyshawn895/Retroactive As an aside, the author's "Technical Deep Dive" is worth a read: https://medium.com/@cormiertyshawn895/deep-dive-how-does-retroactive-work-95fe0e5ea49e https://medium.com/@cormiertyshawn895/deep-dive-how-does-ret...
- andrew_n 7y ago
- bonaldi 7y agoThis was always going to wrong from the minute I read “we had a collection of demos ... and a hard deadline to launch a year later at a Photo exhibition”. That isn’t a real deadline, it’s a management ambition. And a badly set ambition, based on some demos and the belief they could scream good code into existence. Apple is getting better at this - see how it now pulls announced features from releases if they aren’t ready - but it’s still a terrible approach. To make parents work weekends without their children for an entire 6-month period just to try and hit a management fantasy is a symptom of a toxic culture. (And is also counter-productive. The slow and buggy v1 that resulted wasn’t good enough to capture the market — but it was enough to finally wake up Adobe, who dramatically accelerated efforts on Lightroom, which launched first on Mac and went on to dominate the market)
- dmitriid 7y ago> Apple is getting better at this - see how it now pulls announced features from releases if they aren’t ready - but it’s still a terrible approach. It's still mostly "we ship yearly, and everything has to be ready by September". That's how we got four or five iOS 13 updates within a month of release fixing glaring bugs and underdeveloped functionality.
- dylan604 7y ago>Apple is getting better at this - see how it now pulls announced features from releases if they aren’t ready - but it’s still a terrible approach. Is this the corporate version of PTSD? I'm sure the Maps debacle really had an affect on the overall decision process to the "release software prematurely, or delay it until it is working" question.
- caycep 7y agoEven Lightroom arguably hasn't achieved the technical abilities of Aperture...it's slow. Plus now there's a fork of Lightroom "classic" and a weird cloud-only version, and also Adobe's subscription pricing. There are a few other apps that have added digital asset management, but overall, there's really nothing that has taken its place.
- 7y ago
- dmitriid 7y agoWhen I started reading it, I came across this: > “Since this was a professional product, they knew the quality had to be high.” I sighed heavily because instead we got Photos.app. Which is just bad and sad. But then I continued to read about all the management screwups and development hell. And I now I know exactly why Photos.app is such a disaster.
- briandear 7y agoPhotos is amazing. Not sure when you’ve last used it.
- dewey 7y agoI use it at least once a week and there are a lot of places where it could be improved when it comes to stability or making you feel like it's a safe place to store your pictures. I always run into this issue and I'm not alone, some people put their libraries in disk images just so they can properly eject their external disks: https://annoying.technology/posts/ebd70c6c5715bcd8/ https://annoying.technology/posts/ebd70c6c5715bcd8/
- pluckytree 7y agoUntil you want to add keywords... But you're right otherwise.
- dmitriid 7y ago- https://grumpy.website/post/0SUrgqNju https://grumpy.website/post/0SUrgqNju (this is just around sharing) - https://grumpy.website/post/0SZmcHq7V https://grumpy.website/post/0SZmcHq7V - https://grumpy.website/post/0Rz1BBnjz https://grumpy.website/post/0Rz1BBnjz Not to mention that in the time it takes it to sync photos Google Photos can upload a few Instagrams worth of media.
- whalesalad 7y agoThese are the kinds of posts I live for on HN. Stellar inside look.
- mathewsanders 7y ago> Fast forward ten years and the Apple Watch team offered me a job working on SwiftUI in 2015. (The project started on the Watch team). That’s an interesting nugget I’ve not heard before about history of SwiftUI!
- Wowfunhappy 7y agoI wasn't old enough to be paying attention when Aperture first released, but because I've only ever heard great things about the program, I kept expecting this story to end with some miraculous turnaround for the engineering team. That didn't happen. And while the author doesn't say that Aperture 1.0 was bad, he doesn't appear to have thought too highly of it either. Separately, it's hard to imagine such a rushed and mismanaged process producing a stellar end-product (although, I'm sure stranger things have happened). What was Aperture like at release? Were later versions a substantial improvement?
- Terretta 7y agoFor my use, it was fine at release, it got better through time. The unpacking of library and transition to iPhoto compatible library was rocky. Definitely a tool where you wanted the x.x.2 before you’d update a major or minor version, because, well, it probably held 150,000 photos at a time where almost nothing else you did on your personal computer had that amount of data or irreplaceable value per file. --- Aperture science --- Many prolific shooters considered this the best photojournalism / travel / wedding / EDL bulk photo library and photo triage tool outside of the camera bag, bar none. Still is if you have kept a Mac tuned for it. The key benefits for me, not found most other places at the time, were: - auto photo sorting (“stacks” of burst photos you could expand and choose the best from then collapse again, like burst works on iphone now), along with press compliant metadata and tagging, GPS, TZ adjust, etc. - ultra fast photo triage (rapid star ratings and ability to see photos above n stars for fast pruning of a 3000 photo shoot to the best 30 shots), and - a (just okay) RAW engine with non-destructive photo editing, as well as masters and ‘versions’ per photo including automatic RAW+JPEG pairing for digital cameras All this on a love-it-or-hate-it “managed” library, where you could go look at the originals in folders, but never needed to if you let go of folders and thought in metadata sets. (It could also oversee folders external to the library.) I switched to it from Lightroom, occasionally tried to switch back, always felt like molasses compared to the ‘just right’ benefits of Aperture if you shot a lot of photos to get a small set of publishable shots, but also wanted to keep every shot forever. --- Photos 2.0 --- There’s been a dark few years here where the Photos library that was capable of Aperture sized content didn’t offer any of those key benefits in the Photos app, but at least remained accessible across all your devices. While Photos continued to do the RAW+JPEG pairing, it lost most other things. Latest Photos finally puts back in some of the level of photo editing that was in the original Aperture. That said, seems though when implemented through Photos on iCloud, there’s a soft performance limit in the 130K to 160K range that things start to act wonky, one photo out of 100K won’t sync, etc. Be interesting to see what would happen if Apple threw some QA at the high volume uses cases again.
- therealmarv 7y agoSuch a shame that Apple let go of this program... all in the name of their new cloud services. Apple had the big chance to show the world what a joke Google Photos is in comparison... now it's more the other way round in my opinion.