HN user

stirno

428 karma

Founder fluentCODE, Creator of Scrawl and FluentAutomation (http://fluent.stirno.com): Open Source .NET automation framework. Founder, F14N (http://f14n.com): complete platform for automated testing in the real world.

Posts19
Comments64
View on HN

Ya I understand that, if you can get in the door. Those same companies are also the ones I've found more likely to automate rejections of applicants who can't check the right boxes though, making it harder to get in without experience.

Nearly 20 years in now as a self-taught developer.. and I agree with most of what the post says. I would just add that a young person should continually keep trying to get a job, any job, building software. The process of applying for these kinds of jobs helps you identify areas to focus on.

I think the biggest thing that keeps people from being successful is the assumption that, even with all the effort they are putting in, their potential peers are better at the job. In some strict sense that is true but delivering customer value is number one. Keep your focus on that, people will want to work with you. Ignore any feelings of being an imposter.

I got my first contract development gig at 14, first salaried position at 17. Stick with it and make it happen. Be confident. Don't be a dick.

Also, the original question talked about using Java. There is nothing wrong with Java and there are a lot of jobs in that space but I can't imagine a harder place to come in as a young untrained programmer than Java Enterprise development.

There is a pretty important distinction here -- We have seen in the US consulting market (at large corporations) an influx of 90s style contractor arrangements for staff augmentation. This is basically the counter to failed outsourcing efforts. These contractors almost entirely work for large groups like Robert Half, Tata, Infosys, Tek Systems and others.

We also still have a very very strong consultant labor force making 2-3x what W2 full-time employees can pull in. These consultants generally work through smaller consulting firms that take smaller cuts for the placement/handling billing and invoicing.

When teams have problems with remote v local employees, I've found this to be because they actively treat them differently, sometimes without realizing it.

It takes work to establish your culture to work remotely well -- if you just hire some people that you only ever hear on Skype during standup and give them work, they don't become enmeshed in the fabric of the company. Cliques form everywhere but they can be especially brutal in excluding remote workers from the 'core' teams that are seen as successful within a company.

I'm sorry to hear it hasn't worked for you. If you attempt it again, make sure you evaluate whether you've built a culture based on 'being there' before hiring people who can't be. Lots of people make this mistake and just see cheaper workers.

I think your last point about data retention is really the big question. Given the ever-growing use of Parallel Construction in making cases from illegally obtained data (or data authorized only for a different use), its not enough that all these policies be stopped -- we need to address how long they can keep the fruits of their labor.

We're building on/and hoping to contribute to the community Code Fixes/Code Actions being built for Roslyn as far as refactoring goes in C#. We have some plans of providing a similar interface for other CodeEngines to implement diagnostics/fixes.

The font is Input Sans [0]. Great font. We wanted to try and package it with Scrawl but we never heard back from the author. Its free though, go try it out!

[0] http://input.fontbureau.com/preview/?size=14&language=python...

Founder of fluentCODE here. Really happy to see this posted, we just pushed really hard last night to get the site up. Lots of good comments -- I'll just add that we will be a lot more than just a C#/VB/JS editor. We've got plans to build CodeEngines for F#, TypeScript, CoffeeScript, CSS/SCSS/SASS/LESS, PHP, python and lots of framework specific bits for each of those.

We're a small team working hard on a product we believe in. Ask anything and I'll try and respond if I don't fall asleep!

There are several groups working to fill the gap left by VS not running on non-windows platforms (including my own company). There will be options!

Just as a comparison.. In my city outside the valley I'm confident that with at most a week, I could land a brand new gig that meets my previous rate requirements.

And the same is true for virtually everyone here currently playing the software game.

Many very good job markets exist in the US.

I think you've tied your entire response to SQL Server rather than the .NET stack so I'll do the same from an ASP.NET aspect..

ASP.NET is moving at an incredible pace, the new vNext bits are planned to be officially cross-platform and you can support any number of database backends from a .NET codebase.

I also challenge your assertion that better people seem to use other platforms. You can find people marketing themselves as one thing but preferring another in any stack. This is not indicative of anything more than someone needing a job and meeting the requirements of a posting.

Licensing costs can vary. Between BizSpark, DreamSpark and other programs you can get dev tools out of the way quickly. They also provide Windows licensing for the period you're in the program.

The areas where you can get in real trouble as a startup with Microsoft are the add-on product stacks like SQL Server and BizTalk (shudder). I would avoid these in a new product but do not fear building with the .NET platform.

Just to start this discussion off, PVC is a new project that is a great opportunity for people to ease into writing OSS .NET code.

I believe in the .NET OSS community. Its small but growing and we need to bring more people in. I believe in watsi. We're hoping that helping others is a good motivator to get someone to take that first step. For me, that was all that was needed and I've been contributing to open source for 5 years now!

#100 here. Watsi does great things for people and I hope to help as much as I can.

Edit: Its up to 115 people now. Glad to be a part of this community.

This mirrors my own experiences using Gherkin syntax in other tech stacks. The most workable scenario I've come up with is to focus on simple, terse syntax that is still readable.

Build reusable page objects, keep your actual tests short and things get nice and easy.

Lots of good options in this space. A few years ago I built FluentAutomation [1] to solve this issue in the .NET community.

[1] http://fluent.stirno.com/