HN user

ndcrandall

138 karma

Software Engineer and Leader, 13+ years in the industry

ncrandall at gmail

Posts13
Comments59
View on HN
  Location: San Francisco Bay Area
  Remote: Open to all (Remote, in-person, hybrid)
  Willing to relocate: Yes
  Technologies: Ruby, Ruby on Rails, React, React Native, Java, Spring, MySQL, PostgreSQL, HTML/CSS, Javascript, AWS
  Résumé/CV: https://drive.google.com/file/d/1iENUTfuqwvsjW6i9LC-eDyx89h_UCYzH/view
  Email: ncrandall@gmail.com
  LinkedIn: https://www.linkedin.com/in/nicholas-crandall-658849a/
I'm an experienced Software Engineer and Leader with 13+ years of industry experience. Much of my experience includes being an Engineering Manager, but I'm also very hands on, mostly on the backend using Ruby on Rails and Java. I have a lot of experience integrating and scaling 3rd party APIs into backend systems.

I come with a lot of domain expertise in CRM, specifically integrating with Salesforce. I'm willing to explore new domains as well.

I'm looking for interesting engineering roles or leadership positions. I'm flexible with in person and remote roles.

  Location: San Francisco Bay Area
  Remote: Open to all (Remote, in-person, hybrid)
  Willing to relocate: Yes
  Technologies: Ruby, Ruby on Rails, React, React Native, Java, Spring, MySQL, PostgreSQL, HTML/CSS, Javascript, AWS
  Résumé/CV: https://drive.google.com/file/d/1iENUTfuqwvsjW6i9LC-eDyx89h_UCYzH/view
  Email: ncrandall@gmail.com
  LinkedIn: https://www.linkedin.com/in/nicholas-crandall-658849a/
Experienced Software Engineer and Leader with 13+ years of industry experience. Much of my experience includes being an Engineering Manager, but I'm also very hands on, mostly on the backend using Ruby on Rails and Java.

I have a lot of experience integrating and scaling 3rd party APIs into backend systems.

I'm looking for interesting engineering roles or leadership positions. I'm flexible with in person and remote roles.

  Location: San Francisco Bay Area
  Remote: Open to all (Remote, in-person, hybrid)
  Willing to relocate: Yes
  Technologies: Ruby, Ruby on Rails, React, React Native, Java, Spring, MySQL, PostgreSQL, HTML/CSS, Javascript, AWS
  Résumé/CV: https://drive.google.com/file/d/1iENUTfuqwvsjW6i9LC-eDyx89h_UCYzH/view
  Email: ncrandall@gmail.com
  LinkedIn: https://www.linkedin.com/in/nicholas-crandall-658849a/
Experienced Software Engineer and Leader with 13+ years of industry experience. Much of my experience includes being an Engineering Manager, but I'm also very hands on, mostly on the backend using Ruby on Rails and Java.

I'm looking for engineering or leadership positions. I'm flexible with in person and remote roles.

Location: San Francisco Bay Area

Remote: Open to all (Remote, in-person, hybrid)

Willing to relocate: Yes

Technologies: Ruby, Ruby on Rails, React, React Native, Java, Spring, MySQL, PostgreSQL, HTML/CSS, Javascript, AWS

Résumé/CV: https://drive.google.com/file/d/16EC9TJGZjCvxVtfToyHL3cJPRW7...

Email: ncrandall@gmail.com

LinkedIn: https://www.linkedin.com/in/nicholas-crandall-658849a/

Experienced Software Engineer and Leader with 13+ years of industry experience. Much of my experience includes being Engineering Manager, but I'm also very hands on.

In my current role I've built integrations with Salesforce Marketing Cloud and Adobe Journey Optimizer with Java and Spring. I'm also very experienced with the Ruby on Rails framework. I'm open to full-time and contract positions.

This was one of my biggest issues, even as an experienced developer with a CS degree. I always felt a step behind since I wasn't fluent in the latest and greatest framework. All of that changed when I mentally decided to focus on one language, namely Ruby. It's amazing how much you can do with any one language even though it's not fully optimized for a specific use case you need.

So after going back and forth with our startup on SOA or not, I have felt like separating these services out of (in our case) a monolithic Rails application has made sense. I would like to use Sinatra for one service, rails for the web interface, and possibly Python for the last service. I understand this adds a lot of overhead by creating an interface and authentication for each service.

For me the logical division of services seems to make sense especially when using 'the right tool for the right job'

I may be over optimizing, but I think it will pay off at a later date with more developers and the need to scale each service separately. Maybe someone can point out issues with this thinking (besides those addressed in the blog post).

SEEKING WORK - San Fransisco Bay Area or Remote

I'm a Rails developer with several years of experience and a CS degree. My area of expertise is building APIs and integrating with external services. I will build out your MVP quickly or help engineer an existing product. Lets talk in person, hangout, or skype.

Skills

  Ruby on Rails
  3rd party APIs (Twilio, Facebook, Google, etc.)
  HTML / CSS / Javascript

Contact

http://nicholascrandall.com

ncrandall at gmail

The usual advice applies, if you are really worried consult a lawyer. Many will do 30min - 1hr consultations for free and will enlighten you to the risks about your app specifically.

An LLC will protect you from most liabilities and is probably the easiest way to protect yourself in this case. Worst case scenario they sue the company and get all $0 worth of assets from it (assuming no sales).

Applying for an LLC is fairly simple and straight forward. Most states allow you to create one online for less than $100. It honestly takes less than an hour to set them up. Beware the tax implications of doing so, it's a pass-through entity meaning profits and losses are passed directly to your personal income. This is usually not a big deal and most tax software makes this very simple to document at tax time, just keep a record of all profits and expenses.

This is just from experience so take it with a grain of salt. Hopefully this gets you started with some further research.

I overlooked the license that would be created for hosting the source internally. That seems like a good route. I also agree that most enterprise clients wouldn't be interested in stealing the source.

It may just be a legal issue, along with a manual process of checking out the code and installing it on a VM they setup.

Stop Freelancing 13 years ago

The main differences between being an individual vs a company are the intentions for which a client hires you.

Being 'Designer John Smith' attracts companies hoping to lure you in as a full time employee eventually. This can be good for finding work when you don't decline the possibility of full time work, but can burn bridges when you decide to leave the client.

Being 'John Smith Design Studio' attracts clients looking to offload development to another company in order to meet deadlines and get stuff done.

I left work in a way that I believe is less cold turkey and helped ease the transition. Instead of quitting, I told my supervisor that I would like to work as a contractor. My reason for doing so was to live elsewhere and be more flexible with my schedule.

Since I was so valuable to the company at the time, they were just happy I wasn't quitting. After a few months of contracting I told them I was done and by then I had other opportunities come my way. It worked out very well.

I like the idea of a freelance focused market place. I have wanted to build a system for it, but before I jump into it, there are several issues that need to be validated.

How prevalent is this need? Would it need to limit locally craigslist style or is remote possible? How would you facilitate / enforce payment for leads (if not a one time payment)? How should leads be priced?

etc.

I hadn't thought of that, but you're right, it's fairly common to have a retainer with certain contracts. It's related enough fit well into a site like that.

So I've never been apart of a group of consultants, I usually just have personal connections that would fit well taking over the contract. I imagine this is commonly done with other consultants, but I'm not sure of the frequency.

Sometimes I just want to get rid of a client and it would be nice to find an exact fit than refer a friend who isn't totally qualified for the position.

SEEKING WORK, Palo Alto, CA - Remote or on site OK

Currently seeking Ruby on Rails work. Proficient developer in common architectures such as MVC, RESTful applications, and SOAs. Experience includes integrating 3rd party APIs with a recent project implementing a round robin call system via Twilio - http://blumoonlist.com

Skills:

* Ruby on Rails

* Javascript

* Bootstrap

* RESTful APIs

* AWS / Heroku

Portfolio: http://nicholascrandall.com

Github: http://github.com/ncrandall

Email: ncrandall at gmail

Contact me and I'll work with you on your timeframe and budget.

I'll be up late tonight to do the same. Coming back on the market as a Rails freelance developer!

I've heard good things about the prospects of this thread. I tried to find the thread which discussed the outcome of the freelancer, seeking freelancer thread but couldn't find it. There are also many personal references I know of that attest to its utility.

So I have tried to stay away from monetary incentives for users. I would like to foster an open data community and provide more intrinsic rewards for contributing. I would rather monetize the site with extra features on top of the base product. What those features are will be the difficult part.

I'm seeing a trend in the comments here and would just like to add my experience. It is quite similar to the author in that I worked fulltime for a year plus 3 months contracting for the same company.

I consider myself extremely fortunate to have had good health, no family obligations, and low student loan debt (payed off in within a few months of graduating). With that in mind, I can honestly say that there was a ton of pressure to spend money to "better my life". I would get strange looks and comments from friends and family because I drove a '93 Del Sol, and lived in the same apartment after graduating. The only big purchase I made recently was upgrading to a used car that is only 10 years old.

In the end I saved a lot of money. Enough to move back to California, in the Bay Area. I have been living off of savings for 7 months and honestly have about 7 more (conservative numbers). I live comfortably here and I get to work on my own projects on my own time until I make money or run out, in which case I will go find more contract work.

My point is that I decided early what I wanted to do and planned accordingly. I know that I'm in a very unique category with little responsibility. I have much respect for those who can't quite do what I do because of other obligations. This makes me happy and I wouldn't have it any other way. No need to feel sorry for me and think I'm not living life to the fullest, because in my mind I am.

I use Ubuntu. In a past life I was strictly a windows user. The thought has crossed my mind to switch to a mac because of GUI nav speed and peer pressure. It's not that trendy to haul around a 17" Dell XPS with a big power cable to a coffee shop or ruby meetup. Luckily I realize that those good with macs could be equally fast on Ubuntu with practice and being trendy is overrated. It's all about getting things done and I like having a big monitor + power.

I have been using 4.0.0.rc1 for about a month now and have enjoyed the process. There have been a lot of great updates since the previous versions.

I will caution all to be aware of the turbolinks included by default. I spent a while scratching my head why a setTimeout function worked every so often. I had no prior experience with turbolinks or the discussion thereof, though I believe it's a great feature.

My process is a bit rudimentary. I just have a folder with notebook paper in it. When I need to create a new system or subsytem I will draw it on paper just as it would look in any of these diagraming tools. Once ready I'll use lucidchart to replicate the drawing (schema or flowchart). Once it's implemented in code and committed in Git I will go back to the electronic copy, mark in red or other colors anything that will change in the next refactor or implementation. As I refactor I change the red makrings to black indicating it is now part of the system. The paper becomes an artifact of the first revision.

Sometimes I'll break out a new paper and do the initial drawings to test my knowledge of the system and see if I have complicated the design. This system works well for me.