HackerTrans
TopNewTrendsCommentsPastAskShowJobs

andrewcarter

no profile record

comments

andrewcarter
·4년 전·discuss
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!
andrewcarter
·4년 전·discuss
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.
andrewcarter
·4년 전·discuss
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!
andrewcarter
·4년 전·discuss
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!
andrewcarter
·5년 전·discuss
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.
andrewcarter
·6년 전·discuss
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!