It’s been quite a long time since I last posted anything up on my blog. I wanted to share with everyone where am I today and where I’m going tomorrow. Today, I sleep in New Jersey and work in Midtown New York (two blocks from the Glass Apple Store) at a company called Rejuvenan Global Health. I’m an iOS Engineer. I enjoy the projects that I’m working on and I’m always challenging myself to learn something new every single day. I was very nervous about moving up to the NJ/NY area. I had just graduated and literally a month later I’d landed a job in one of the largest cities in the world. However, when you get your first real job (out of college or school or wherever) you’ll find that a majority of your time is taken up by that job. I thought I would have more time for things now since I didn’t have homework or exams to study for. But no, I was wrong.
When you account for a 45 min train ride to New York, walking from Penn to 57th street, working for 9ish hours, and walking back to Penn, and finally getting home after rush hour train traffic, you start to prioritize what you want to do when you get home (don’t forget dinner!) I’ve started to pull myself away from random reddit searches, reading blog posts about obscure things, and checking out what people are working on via twitter. I’ve even deleted my Facebook account. Instead, I’m spending more of my time reading blog posts about iOS development, software design patterns, and reading some popular open source iOS libraries on Github. I want to get further in my career and to do that I need to soak up how to quickly solve problems at work.
When I was coming up with a list of things to work on this year, my list kept growing and growing. My refined list includes: test driving every piece of software that I write from now on, learn reactive functional programming, and getting better at iOS design via Autolayouts and UIKit.
I’m currently working on a team with 3 developers (one UI/UX Engineer, 2 Systems/Backend Engineers) and they are all test driven. A majority of our standup talk revolves around testing. That’s because when you’re trying to build a platform with a small team, there isn’t much room for error. Any error that occurs in the platform is known by a member of the error domain before it happens, all through test driven development! So, I’ve decided to test drive every piece of reasonable software that I write from now on. This means going back and writing tests for each older project I have on Github.
If I had more time I’d like to learn functional programming with Haskell. I’ve spent a few days with Haskell but nothing serious (not yet). Instead I’m going to learn reactive functional programming by using a framework called ReactiveCocoa. ReactiveCocoa is a Cocoa framework inspired by Functional Reactive Programming, by providing APIs for composing and transforming streams of values over time. I believe functional programming will help me solve a vast majority of problems I have at work.
I feel very comfortable with Objective-C and various software design patterns such as Model View Controller, Abstraction, Singletons, Adapter, and Delegation (to name a few). However, I’d like to get better at the look and feel of building an iOS application. I’ll be the first to admit, I suck at Autolayouts, but soon enough I’m going to master it. This means spending a majority of my time getting better at Autolayouts and UIKit, by spending a lot of my time in a repo called Ray. By the end of the year, I want to be able to build views without interface builder.
Thank you for reading my update! Stay tuned to read blog posts about building network controllers using NSURLSession and test driven iOS development using XCTests and XCUITests!
This blog post serves as a gentle introduction to LaTeX, the documentation preparation system and docmentation markup language.
This semester I decided to write my reports from my Analysis of Algorithms class in LaTeX. This was not a difficult task to accomplish, it actually made writing these reports easier (and prettier). Before diving into installing LaTeX packages and setting up your first LaTeX document, let us begin by looking into the history of LaTeX.
History behind LaTeX
TeX is a typesetting system written by Donald Knuth in 1978 and is still used for typesetting complex math formulas today. LaTeX is written in TeX and, like Tex, was designed “to allow anybody to produce high-quality books using a reasonably minimal amount of effort, and to provide a system that would give exactly the same results on all computers, at any point in time”.
LaTeX/TeX is still quite popular in academia in areas such as mathematics, sciences, and economics. You may have actually read a few books that were written in LaTeX (and you didn’t even know). But, did you also know you can create beautiful resumes and CVs with LaTeX as well? Excited yet? Let’s begin installing LaTeX on your machine!
On Windows 7/8, download MiKTeX from here.
On Mac OS X, download MacTeX from here.
On *Nix System, just check your distribution’s package manager for “xelatex”.
If you have any issues installing LaTeX, just follow this link for more download instructions.
Setting up your LaTeX file
This is an example from a report I wrote in my Analysis of Algorithms class. Remember that LaTeX can still be used for all kinds of documents (not just computer science reports).
Above is a portion of code that serves as the “header” of your LaTeX document. The header of the page includes the documentclass, packages, specific fonts, etc. The “header” can be extended to include much more than this including custom layouts for various kinds of documents.
You can look here for more information on creating your own .sty files.
Above is the portion of code that makes up the “body” of the LaTeX document. The body is where all the contents of your document are contained. In example below, I have included a Title, Author, and Date Tag (which is created by the \maketitle tag), an Algorithm function and an example table of CPU clock cycle times in Milliseconds.
Compiling your LaTeX file
To compile your LaTeX file to pdf format, run the following command.
If you run into any issues on compilation, first read the compilation error and enter ‘r’ to finish compilations.
You can also use an online LaTeX editor such as WriteLaTeX.com.
Many LaTeX concepts can be learned from the example file, however you can learn way more by just diving into LaTeX (which ultimately helped me the most). Also, I feel as though LaTeX has helped me better structure and think through my reports for class. I hope this post was of some use to you!
Please comment below with any questions or concerns. Thanks again!
Extra: Here is an example of a LaTeX resume.
Lately, I haven’t had very much time to write blog posts and work on the projects that I want to work on. Instead Analysis of Algorithms and undergraduate research has taken a significant portion of my time. However, I did start writing my papers in LaTeX which has actually been a fun experience and pretty easy to learn (and you get pretty reports)! Also, I’ve started to gain in interest in Video Streaming development from the undergradute research project that I am working on. My time management has been out of wack lately too, need to fix this problem. My algorithms class has been kicking my butt, however I’m enjoying the material I am learning - especially dynamic programming (very interesting concept). You can find the algorithm projects that I have been working on here.