![]() On weekends, I usually wake up at 7AM and do the same, but I usually stop around 9AM and enjoy the free time.įor a person working from home, the most important thing is self-control and the will to push yourself to work. I answer all support queries that are pending and then I focus on the actual development. I'm an early bird, so I wake up at 6AM, grind the coffee and put the coffee drip on, and sit down at the computer. ![]() I think that like most developers, I like order. an app that builds all the other apps and uploads them to all distribution channels.īesides the tools, what routines help you get your work done? Software-wise, I use Xcode along with a few in-house made apps for helping me with managing localizations and app distribution - e.g. Nevertheless, when I'm on the go, I develop on a MacBook Air (M1) and I don't have any issues with that (other than the small screen). I currently run an iMac Pro with a second display, but am eyeing a Mac Studio in the future (waiting for an upgrade). Of course, the faster the computer, the faster the compilation, but you usually only feel this when you are compiling release builds for the public. ![]() Even low-entry Macs are powerful enough to compile the apps quickly enough so that you don't need to wait for longer periods of time. Nowadays, it's becoming less important which computer do you have. What tools & gear do you use? (Could be hardware, software, something else entirely.) Usually towards a more efficient and better design of the app (internally, we're not talking about UI). It seems like some unnecessary evil that would get pushed onto you at school, and I'd seen it this way back in my school years as well, but it turns out that it changes your perspective on how to do things. Even if you develop web apps, it's all quite connected. Go low and start with how a CPU works, what are instructions, learn about syscalls, about algorithm complexity. When you see something on your screen, it always appears a bigger accomplishment than spending hours on some algorithm that doesn't show on the screen, but allows more efficient computations in the background and therefore more responsive app for the end user. It's nice to learn how to make some UI with a few lines of code. I cannot say that I'd recommend that to everyone, everyone needs a different approach.īut what I'd stress out: don't forget the basics. I was always a bit of a self-taught man, so as I dug around the system, I experimented and learned from my mistakes. What resources would you recommend for people that are interested in what you do?Īpple has a wide range of sample projects and sample code on their site, ranging from simpler to more complex, so that's always a good place to start. Reading this back and seeing all the now-defunct services and apps, kind of makes one feel a bit old □ I actually had my first shareware apps out on the Internet when I was 15 or so and I sold license codes via Kagi which was an e-commerce platform back in the day and I remember getting the first check and being so excited about this. As I dug more and more into the system, I got more and more interested in creating something as well.Īt first, I got to play around with Pascal, then REALbasic (now Xojo), and finally, at the age of 17 or so, I got to learn Objective-C. Initially, I was quite happy just digging around the system and peeking around with ResEdit (ha! Who remembers this gem? ). This got me interested in the computer world in the first place. My father is a freelance graphics designer (now retired), so computers (Apple ones at least) have been around the household for a long time (since 1993 or so). This is why to this day, I like to answer my customers' support queries myself instead of hiring someone. To me, it's always frustrating getting support from someone who has learned a few phrases, but has no idea about how everything works. So I started my own software company, built a few apps (and acquired a few along the way), focusing on communicating with the customers myself. I'm a person who graduated from a college (software engineering masters degree) and decided not to contribute to someone else's dream, but rather to build my own one. An interview with Charlie Monroe, developer of Permute & Downie, as well as a published poet.
0 Comments
Leave a Reply. |