andrewcarter

At the company I work for PiPs _usually_ lead to issues being solved. There are several developers I've worked with on PiPs (we do specific mentoring and follow ups on the areas of concern) that were able to improve and are now doing great. It isn't always a terrible thing, certainly not comfortable for the person on the PiP but it can be a positive thing in the long run!

The Home app now supports a dynamic color option by default which changes based on the sun / lighting in your condition. Seems to work- I think it showed up for me about a year ago or so, so it's pretty new.

I've felt a lot of the same frustrations on iOS projects with swift. Lots of people add tons of extensions and helpers, and folks learning on these codebases don't learn iOS, they learn the playground that the developers of the project made, it's not obvious what's built in and what's custom. The extensions are less composable, harder to navigate, and often end up really ramping up complexity when you end up with constraints and generics and protocols and all kinds of really fancy "nerd stuff" that really isn't needed in an iOS codebase. I used to have a theory that folks did this because, well, Apple has basically "solved" what make an app is. Everything you need is there, it's all pretty easy to use, it's "boring" in a good way. Maybe this is how developers scratch the itch of needing to do a lot of "real programming"? Maybe I'm just getting old!

I learned to play the fiddle the past two years working from home during Xcode's abysmal compile times. Sadly my new M1 max whatever has solved that problem, ha!

swift is by far an easier language, safer language, and has a lot of power and nice functional bits, but _oh my god_ those compile times and the lack of a stable debugger and refactoring tools can make it miserable to work in. That and ever since swift 4 or so I feel like we're leaning towards the c++ "everything and the kitchen sink" kinda problems when it comes to features. Used to be there were fairly obvious "right" or idiomatic ways of doing things, but now it's gotten a lot more complicated. Property wrappers, combine, all the stuff with opaque types and the insane stuff you can do with protocols and protocol extensions, all the fad architectures and patterns. Most swift codes bases I've worked in are highly over engineered and kinda feel like the developer of the project just learned about X cool thing in swift and wanted to use it everywhere. It's amazing how the crash rate of apps I've worked on in swift are like consistently less than 1%, it's easy to learn, very modern feeling. But gosh some days I'm just longing for some classic objective c spaghetti code that compiles instantly and gives me that great debugger I've come to rely on. Oh and don't get me started on the abysmal auto correct, code completion, and error messages. Swift still has a ways to go IMO, but I do think it's the choice for an iOS app in 2021- just be thoughtful about which language features you use and not going bananas with extensions and protocols.

Why do Java developers wear glasses?... Because they don't C#

EDIT: Ah someone already did that one- what's a ghost's favorite variable type? A BOOlean

I hated standups until we eventually got a great PM who moved to something like this, and now I try hard and make standup run like this on any project I'm on. Jira has this nice feature where it puts a little dot on something for each day it's in a column. Standups largely turned into scanning for things that had > 2 dots on a ticket from right to left, and discussing what we needed to do to keep things moving through the system. Love it!

I have a problem cutting people off- I get way to excited about what I want to say and jump in. I really appreciate when people call me out and don't take it personally. I also try to work on it and try to help steer the conversation to other people who have been cut off when I see it happen. So IMO don't be afraid to politely just let someone know! If you don't feel comfortable during the meeting, maybe speak with them afterwards, doesn't need to be a big deal, just let em know. If you don't feel comfortable being a little confrontational, speaking with manager types or even just before a meeting indirectly bringing up that everyone should focus on it can help too.

I know sometimes people cut off others very purposefully or in malicious ways, but it sounds like maybe where you're working that's just how it is- so everyone kind of has to play the game to be heard. In that case, try and change the game! A little bit of discomfort now can lead to yourself and probably others being happier down the road.

Reminds me of something I pulled in middle school - back when we delivered papers on floppy disks. I took a garbage binary file and renamed it to `mypaper.doc` or whatever, turned it in on time and got a free weekend to finish it because my disk "was corrupted" :)

Really cool tool! I've been getting into more theory stuff after playing guitar for quite a while, so it's awesome timing! Thanks!

I think you're right that I've likely selected countries that I didn't need to, but I'd rather be safe than sorry.

I'm not storing any data other than a day of the year and wether a pill was taken. It has Google Analytics and a crash reporting tool in it, and I'm not sure how those play into the whole thing.

I have a little birth control pill reminder iOS app I made like 7 years ago that I still maintain in the app store. I don't make really any money off of it but I keep up with it because it has a good amount of users. I don't THINK any of the GDPR stuff falls under anything the app does, but I sure as hell aren't taking any chances. I just removed it from any country that fell under "Europe" in the app store. I guess my point is I agree with what you're saying, and here's an example of a little hobby app that GDPR killed for EU countries. It's not worth my time, money, or risk to bother with it.

Me too! I love QBasic so much - totally wouldn't be where I am today without it. I met a kid at summer camp when I was in middle school who told me he made his own games and fake computer viruses to scare his parents in Quick Basic. He mailed me a floppy disk with Quick Basic on it once we were home and I've been in love with programming ever since.

It's was the perfect first language. It's so easy to play little sounds or draw graphics, and the environment is basically non-existent so setup is easy. So much fun!