Suggestions
Moshe Berman
Experienced iOS Developer & Software Eng | Skilled in Obj-C, Swift, Python
Moshe Berman is a skilled software engineer with extensive experience working with Objective-C and Swift. He has worked at prominent companies such as Apple, The New York Times, and Facebook. Moshe is passionate about developing user-facing features and APIs, and has worked as a freelance iOS app developer in the past. He studied computer science at Brooklyn College and has worked for organizations such as OWAL, GameChanger Media, and CityMaps.
With a background in computer science and software engineering, Moshe Berman's expertise lies in developing and designing user-facing features with Swift and Objective-C. He is skilled in working with APIs and has experience in developing iOS applications. Moshe is proficient in collaboration and working extensively with various companies. He is passionate about designing applications that enhance user engagement and innovation, expressing its interest through freelance iOS app development as well.
Highlights
Come work with me on iOS infrastructure!
• ForeFlight launched with the iOS App Store, and with the Vision Pro. • We’ve won awards and our customers are dedicated. • I’ve got a great team and manager.
We’re looking for someone who has experience with mixed codebases and gets the nuances of Objective-C and Swift interop.
You can apply here:
https://lnkd.in/ezbschGy
(If we’ve worked together, ask me about a referral.)
Not an iOS polyglot or even an iOS engineer? We have other technical and non-technical openings at https://lnkd.in/eQNqjaf7
How do you and your team prioritize code review, to ensure it’s not a bottleneck in your development flow?
Code review is an opportunity to prevent tech debt before it is incurred. It’s a way to reduce the bus factor by allowing teammates to ask questions. It’s a teaching opportunity. It’s a learning opportunity.
Most engineers can recognize these benefits, yet it’s not uncommon for code review to happen unpredictably or inconsistently.
“I’ll get to it first thing tomorrow” is a well intentioned refrain. Sometimes it’s followed with “A fire came up. I’ll look now.”
As a software engineer, I get it. Context switching is harder than staying heads down. Reading code is harder than writing it. But, reviewing code is better for business than procrastination.
I wonder about SLAs or code-review on calls. Another solution that’s been suggested to me is pair programming. These all have pros and cons.
I’m noodling on timely code review.
What do y’all think?
