mysticllama
Joined 13 years ago
Joined 13 years ago
the first time this happened, i felt like my brain was going to explode -- so wait, you want me to leave the main app feed broken and people pissed off because the comment-notes-experience-home-ex team's weekly comment rate is slightly regressing?
writing this out, not sure how i lasted as long as i did.
The App Store disclosure you're referencing means these data can be aggregated and associated with your identity, but that's just the nature of using any social media app that serves ads these days.
early in my career, i shared this hangup and because i was so emotionally invested in the products that i worked on, i considered criticism of my work == criticism of me personally.
i think the next step is evaluating how effectively you are separating your work and personal life. when i have struggled with this issue the most, it has correlated with me being too emotionally invested in what i'm working on.
make sure that you have projects and interests outside of work that fulfill you so that you don't rely an outsize amount on your work for fulfillment. often this means having better guardrails about work-life-balance -- do you clearly define when you are and aren't available for work, for example?
the other thing is simply reminding yourself that your work isn't you, and it doesn't define your value. working with complex systems, we are going to screw up at times, it's an inevitability. if you aim to not make mistakes, ever, and bristle when they are pointed out or criticized, you're going to struggle over the longterm to get along with the people you collaborate with.
ironically, i have found that being more open and accepting of the "dumb" shit i do leads others to think more highly of me as an engineer. i think most of us can think of "that person" we've worked with who can't take criticism and recoils when questioned -- when you do, how did that you feel when you experienced that behavior firsthand? if i had to guess, it probably wasn't positive. we can do better!
i remember getting it right after it came out -- i had just turned 11. when i tried to explain to people that it was a massive, detailed fantasy world where you could go on adventures with people in real-time, they'd look at me like i had two heads.
this got me into scripting and mods and was a big influence on why i became interested in software and hacking, and have had a career in it since.
if you try to cover every base and fret about everything being optimal, you're going to barely have time to get started.
it depends on your learning style of course, but if you like lecture / course-style learning, i highly recommend paul hegarty's CS193P, it will definitely give you the in-depth, conceptual explanations you're describing.
while it is an iOS dev course (taught at stanford, lectures are freely offered online), the newest lectures are using swiftUI for UI, so pretty much all of it will translate to doing macOS dev.
paul is a cs prof at stanford and worked at NeXT and then on the objc lang many, many years ago, so he's been doing this a while and knows a thing or two :)
i remember having a conversation with a LICSW who did a tremendous amount of work with drug addicted and homeless populations; she explained that when she really needed to, she could "beg, borrow, or steal" a way to find better housing for someone, but that really wasn't the crux of solving the individual's problems, it's only one facet.
even if someone who has untreated mental illness or drug addiction suddenly has a great new place to live, they're not going to stay at that address long if their other needs aren't treated.
i'm not saying there shouldn't be more affordable housing ASAP, or that it wouldn't radically improve some lives, but i get the impression that a lot of folks think homelessness is mainly a housing problem when it's really not so simple, and i think that needs to change if the problems have any chance at getting improved.
pros: there is no shortage of roles, my experience has been (especially now) that skilled ios devs are always in demand.
it’s fun to work on mobile software, imo —- you get to live in a cool space where good software and good UX are both essential. hopefully you like doing lots of UI debugging and thinking about performance.
you get to work a lot with product and design on almost any consumer mobile app you dev for. fun if you like collaboration
cons: for the same reasons a niche is a good thing, there’s an eventual ceiling. you could probably sell your mobile experience and jump into an android or maybe front end web dev, but it’s easy to get “stuck” which is bad if you like versatility
there are definitely some annoyances in dealing with the “walled garden” or whatever you want to call it.
app store can arbitrarily decide you can’t visually style your app a certain way anymore (had this happen)
provisioning devices is annoying though has gotten less bad
i could go on… i’ve done it a long time and made a career out of it and really enjoyed it! if you like the idea of making products that are in people’s hands day to day it’s the right way to go.
since, i have decided to abandon even "white lies" and i find it very freeing. in the long trail i think it makes life a lot simpler, even if situations arise where you feel as though you need to "spare someone's feelings," i've found that they're navigable in a considerate way that doesn't necessitate dishonesty.