Search Results

Search found 3 results on 1 pages for 'suslik'.

Page 1/1 | 1 

• How to justify technology choice to customer?

  - by suslik

  When freelancing / contracting a customer will typically specify functional requirements, acceptance criteria, etc, and the implementation details are in the developer's hands. As a developer your technology choice is a balancing act between what you are most familiar with, technologically what the right tool appears to be, ease of finding coders with this skill and their expense, and a few other factors. I'm in a situation where I have evaluated my options and selected a somewhat obscure open source technology that I believe will get me there faster, easier, and be more maintanable in the long term. It's different, but I think that that is what the requirements call for. The customer has inquired about what I'm going to use to build the solution, and now they are concerned because they've never heard of it before. The reasons for my choice are mostly technical, whereas the customer isn't (but they know some buzzwords!). Explaining these technical reasons will not be easy, and I am not sure if that is the right way to approach this situation anyway. And that's my question: what is the right way to approach this situation so as to cause the least amount of headache for everyone involved?

  Read the article

• Hiring developers - listing IDE as a requirement?

  - by suslik

  I've been looking at some job postings and noticed that a fair amount of them list IDEs under the 'required skills' section, even for senior positions. This is not localized to one company either, but rather it's something that comes up once in every few postings. I am perplexed by this job requirement, as my mentors and some of the best coders I've seen in my life were VIM/Emacs ninjas. Similarly, when I work with people I don't much care what tools they use as long as they are productive on the team. Can someone please explain the rationale behind hiring managers making IDEs an official job requirement?

  Read the article

• Business Analyst vs. Architect [closed]

  - by suslik

  I'm a developer of a few years in the financial industry and will soon need to decide what career path to try and row towards. Broadly speaking I have two options: something more 'people' oriented like BAs, or keep coding and try to make more technical decisions like the Architects do where I currently work. Here are my perceptions right now: Business Analysts: get paid way more than devs once they do their job, it seems like they usually have no worries more likely to go REALLY high up in the organization (VPs, etc) Architects: things like certification matters (I see this as a con) called in when things go wrong more than anyone else (weekends & overtime) long career path to get to (dev - senior dev - team lead - architect) I would find the latter more intellectually rewarding, but when I look at it I just can't justify it in terms of lifestyle. Am I wrong / what am I missing? Can you really make a lot of money in a technical role or must you really get out of coding? Thank you for any constructive input.

  Read the article

1