490 karma · joined August 7, 2007
I'm a C# dev... and it feels a lot like going back in time working with other toolchains sometimes (especially on the SQL side of things).
If tax rates were higher I'd hire people, buy office space or equipment. Anything to keep me from having to just gift it to the idjits in Washington.
Networking and contacts (and I mean legitimate networking) really play a big part in your overall success.
I'm in a large city, but nothing like NYC or the Valley either.
Bad devs write bad code. Beginner bad devs tend to write their bad code in Access (or Excel). It gets the job done --- until it doesn't.
I told them... listen, we can get real expensive, really fast. So if you help me, I can help you. They build specs in powerpoint, excel, paper etc. We discuss them (in person typically at a scheduled meeting where we discuss these features as well as business consulting about where to take the business, how to grow it, what features have been requested, what to add, etc.). My team then develops what they want.
The customer then QAs the software to make sure it's good. This saves them a TON of money.
They're happy, I've got an easy client to work with and my devs enjoy working on the project because the requirements are well thought out. My client is happy because they're getting a good value (both in terms of less $ on dev and the money they spend on business consulting is put to better use since they've done their homework).
Contrast this with another of my clients (with a larger, but dwindling budget). They typically say "go develop x" with no real guidance. We develop X, but once they see it they say "that's not what we wanted." After a few cycles of this, and frustration from both sides, we simply now say "you've thought about X, why not tell us what you've got in mind so that we build the right thing first?" It's made things move a lot smoother... enough so that this client is now extremely aggressive in their release cycling (and it feels like a hamster wheel)... which we're working on... (including charging 2x for forced weekend work - "It's Friday at 3pm. If this must be deployed Monday, then we're going to have to work over the weekend and that is at $xxx rate." We've not worked weekends for them since :)
Craplets in 2013?
That said... B2b means you'll have to provide better support (contracts etc).
Of course that's subjective... And impossible to compare dev a using tech 1 vs dev b using tech2.
http://www.greenleafbookgroup.com/blog/2011/10/12/whats-the-...
(etc. etc. [seriously google it if you're interested])
I agree with shawn-butler -- I think the lack of English documentation/implementation is huge.
.NET web application developers
I've got a couple positions open for .NET devs. Full Microsoft stack. Working on public and internal facing applications.
We do a bit of mobile development as well.
Shoot me a resume/intro to sgoodpasture at thirdcorner.com
Company: Third Corner LLC www.ThirdCorner.com
Seeking: Designer
Duties: Designing web sites, web applications (public facing and intranet), mobile applications, marketing materials (the full gamut from logos to banners to letterhead) in both raster and vector. Ideally you can slice stuff and if need be get your hands dirty in the code. Human factors experience a great plus as we're very user centric.
Seeking: ASP.NET C# developer
Duties: Our typical project is a 1 to 2 month project with a lead developer and a junior developer. This is for the lead developer. You would be reposponsible for all aspects of the project (database design, architecture, front end experience , etc.). Designs will be provided by our design team, but they are the base and you have authority to make changes as needed. Of course you need to be able to write HTML, CSS and JavaScript. We have a core project template/libraries that helps accelerate development that you'd help enhance and maintain with the other lead developers.
You would also be responsible for investigating new tech and helping then company make decisions on its usage (mobile toolkits, data bases, reporting, payment gateways, etc.).
About us: we're a small consulting company with a track record of developing applications quickly and effectively. We pride ourselves in being able to use our business knowledge and user focused development ideal to build the right thing first even without traditional requirements (ie we're really good at taking the sketch on your napkin and making it happen quickly).
How to apply: email your resume and an into to info at ThirdCorner.com
No... we just can't afford to waste our time with people that would rather discuss esoterically the merits of x vs y than actually get work done.
One that sticks in my mind is one of the first "real" jobs I had. The company was a solid, well established company that was about 20 years old. Best place I ever worked. They had a piece of supporting software that was written in VB on Access. The software was basic, but it worked as a great support to the methodology and theory of the company.
One big (REALLY BIG) client came in and needed the software to be housed on central servers, with the ability to roll the data up for reporting purposes.
So the company went off in the weeds, building a huge (2.5meg!) java applet, basically tailored to this one client's specifications. The company had no java experience. Had to hire java guys. No Solaris experience (as required by the client). Had to buy hardware and hire people. They had no oracle experience. Again, more $$ and more people.
Within 3 years the company went through two acquisitions, one of which was a reverse buy out of a crappy company that had IPOed. A year later the company folded.
A 20 year company was destroyed by this choice to build a bespoke system for a huge client.
Another memory is making said 2.5meg craplet run under the IBM JVM for OS/2 Warp 3. On token ring. Banks got sold some horrible systems!
I renegotiated more equity with the last round of work.
I talked to him tonight and we're going to get the paperwork updated and get everything squared away now that things are picking up. He also got sold a key man policy, so there's some paperwork there that we have to do.
The one thing I guess I didn't highlight well enough was that we were lucky to be presented with a way to change our business that would allow us to shift into a better market space. We were even luckier to recognize it and jump on the opportunity.
I think that a lot of the time people go heads down and start rushing in and when presented with an opportunity to shift, they don't see it or are unwilling to make the change.
I guess "Be Flexible" is what I'm trying to say.