hidden_sheepman

Location: San Diego, CA

Remote: Negotiable

Willing to relocate: Yes

Technologies: Ruby, Go, Python, Swift, Objective-C, C++,JavaScript, Bash, SQL(MySQL, Postgresql, Sqlite), Redis

Résumé/CV: Will send via e-mail

Email: tuttza at gmx dot com

It’s truly a bad thing when your role starts to change because of their vision, idea etc

Checkout: https://github.com/coteditor/CotEditor

If your into BSD* OSes then you might like: http://daemonforums.org

You could looking to using: http://template-toolkit.org/

This is a pretty solid list for someone looking to get into cpp. I would add another section after pointers about using smart pointers.

I think I care either way, there is something about that cup of hot black coffee while digging into an unsolved problem.

Nano, is great, very light weight, and easy to compile from source. Usually available on pretty much any unix system.

I love the fact that it doesn't try to do anything more than edit text.

Custom complex workflows

Yes, and with being a member, you get access to the farming skill!

It’s refreshing to see a different alternative to current trend of SPA’s frameworks.

Dokuwiki, easy to setup and works great.

It takes time. The more experience you have with the project you're working on the more ideas you will have to either apply to the project itself or create a new project to help support it.

Not sure if it has been mentioned yet, but checkout Tutanota https://tutanota.com/

I love the simple interface. They have apps both Android and iOS and they have a free version and paid version 12 euros per year.

The dev tools are still way to slow. Especially when debugging javascript. Sometimes there is a 40+ second wait when your trying to go from an error in the console to the line of js in debugger.

I miss the days of expertise, you expect doctors to specialize, why can't software developers specialize? I get the point but, its really hard to expect someone in the software industry to be top tier at something when they are expected to know everything.

Basically I think developers need more focus instead of the industry expecting us to know everything. I am not saying that we shouldn't know or try to learn different things, but its really hard to become the best when your spending your time on frontend, or backend or tweaking the database or algorithms there is just so much going on. people just need time, just like doctors need time to become a good doctor, developers also need time. People who really get this understand how to build teams and good engineers in which inevitably leads to a good product.

These are my top 5. Usually I think its common sense especially if your the one applying for the job, one would assume that you want the job if it was offered to you.

1. Is the job described what your actually going to be doing?

2. Team/Company Culture, did you meet the team? how are the managers? the company values? etc..

3. Salary expectations (whatever yours is or anyones is) don't be afraid to negotiate if you feel its to low.

4. Do you see your self here for more than a year?

5. Room to grow, do you want to become a manager? or a senior developer? what options are available to you?

after reading this article it made me think about and episode of Scrubs I was watching the other day, where Dr. Cox made a decision that led to 3 deaths of his patients and after he was afraid to make decisions during the episode. I thought to myself it must be difficult to make a decisions that could affect peoples lives, would having a machine help make those decisions easier an more accurate?

I mean sure you have doctors that have 20 years of experience but still get the diagnosis wrong even it if it's close, but still it seems that compared to machines that get feed large amounts of data still come up short to. I think saying machines will replace doctors is the wrong approach, in the article one of the doctors interviewed said "If it helps me make decisions with greater accuracy, I’d welcome it”. Thats we need more tools that enable doctors to make more accurate decision than going on an experienced hunch.

I think it's great this subject is being explored it will help more people, and doctors do their jobs even better.

There is nothing wrong with Php, I would think that if your worried about companies looking at your resume I think they would be concerned more about the project you wrote than the language it was written in.

To add to this comment, Solving problems is more important than the language you implement the solution in. You can write good Php code and the same goes for any other language. At the end of the day the result is what matters. I personally think your putting to much emphasis on the language.