|
I'm not suprised. Your employer lucked out.
/ravi
|
|
|
|
|
You now.
Let us know a few weeks from now.
Once you lose your pride the rest is easy.
In the end, only three things matter: how much you loved, how gently you lived, and how gracefully you let go of things not meant for you. – Buddha
Simply Elegant Designs JimmyRopes Designs
|
|
|
|
|
...a few weeks from now:
Why Contracting Sucks Today
|
|
|
|
|
«I'm asked why doesn't C# implement feature X all the time. The answer's always the same: because no one ever designed, specified, implemented, tested, documented, shipped that feature. All six of those things are necessary to make a feature happen. They all cost huge amounts of time, effort and money.» Eric Lippert, Microsoft, 2009
|
|
|
|
|
well done - guess we'll be seeing less of you here then
|
|
|
|
|
Garth J Lancaster wrote: guess we'll be seeing less of you here then
Either that or my gf will be seeing less of me. It probably means fewer articles for a while, as this is a full time contract position, and frankly, I'm looking forward to banking some of the $.
Marc
|
|
|
|
|
Marc Clifton wrote: Either that or my gf will be seeing less of me. I guess your gf can help you with that question
- Sebastian
|
|
|
|
|
Congratulations - and now the real work is over you can enjoy your days!
- I would love to change the world, but they won’t give me the source code.
|
|
|
|
|
Congrats! Goodbye to horrible SQL procedures and hello to other horrible SQL procedures (everybody has them, no? )
My blog[ ^]
public class SanderRossel : Lazy<Person>
{
public void DoWork()
{
throw new NotSupportedException();
}
}
|
|
|
|
|
Sander Rossel wrote: Goodbye to horrible SQL procedures and hello to other horrible SQL procedures
Nah, this is goodbye to SqlServer and hello MySql. Hmmm. Hopefully it's matured from when I tried it several years ago. No SP's, but this is Ruby on Rails, so probably everything is ActiveRecords.
Marc
|
|
|
|
|
Marc Clifton wrote: MySql [...] Ruby on Rails [...] ActiveRecords. Don't know any of them (or should I say I haven't worked with them?)
Sounds fun though
My blog[ ^]
public class SanderRossel : Lazy<Person>
{
public void DoWork()
{
throw new NotSupportedException();
}
}
|
|
|
|
|
Yeah, well done!
In similar news, I got the job!
|
|
|
|
|
Well done and congratulations.
|
|
|
|
|
Thanks Peter!
|
|
|
|
|
Gratz
|
|
|
|
|
Congrats
New version: WinHeist Version 2.1.0
My goal in life is to have a psychiatric disorder named after me.
I'm currently unsupervised, I know it freaks me out too but the possibilities are endless.
|
|
|
|
|
|
Awesome.
|
|
|
|
|
I am curious about other peoples views here. But this is my take on this is,
in ROUGH Order:
1) Analysis Skills (Breaking Down and Understand problems)
2) Programming/Testing Skills (Strong desire to test code and at least regression testing)
3) Skills using Tools (Excel, grep, etc)
4) A desire to learn new things
5) Communication Skills (Letting people know what the trade offs are, and impact of changes, etc)
6) People skills a plus...
So, strictly speaking, a severe introvert can easily be a developer, but will have issues with the last two items. Some times you want this person on the team (they write what other developers use).
I am thinking about this, as I am an older programmer who is talking to more young kids about careers in software development.
Anyways, it is interesting that managers just invert the order (LOL, almost kidding).
Are there any other skills... I am trying to create a Graphic of "sized bubbles" indicating
different types of programmers based on depth of enjoying each piece...
|
|
|
|
|
A sense of humor because there will be a lot of times when you want to say "are you f***ing kidding me" but realize it is a rhetorical question.
Once you lose your pride the rest is easy.
In the end, only three things matter: how much you loved, how gently you lived, and how gracefully you let go of things not meant for you. – Buddha
Simply Elegant Designs JimmyRopes Designs
|
|
|
|
|
The only weakness I see in your list is 4 -- by stating it as a "desire" it tends to become an end-in-itself.
Which leads to "I need to learn something new, what can I learn?", and that can result in the problems expressed in So many frameworks...[^] when the developer now wants to throw everything he's learned at a problem regardless of whether or not it adds positive value.
This is made worse by employers (including mine) pushing employees to learn stuff just so they can put it in an annual review and check off "personal or career development".
Directed learning -- seeking and trying tools to help with an existing and immediate problem -- is necessary, so willingness and ability to learn new things is important.
|
|
|
|
|
PIEBALDconsult wrote: Which leads to "I need to learn something new, what can I learn?", What would be valuable for me to learn?
I don't understand most humans, so I went for a dip into psychology. I still do not understand humans, but the insight that we are all lunatics was very valuable.
Bastard Programmer from Hell
If you can't read my code, try converting it here[^]
|
|
|
|
|
PIEBALDconsult wrote: This is made worse by employers (including mine) pushing employees to learn stuff just so they can put it in an annual review
All of what you say is definitely true.
I think what you we are all looking for is, "The ability to implement the correct solution after weighing the trade-offs of each."
Instead of, "I just learned this cool new technology and I've jammed your software into it"
|
|
|
|
|
Great Point!
This gets into continuous improvement as opposed to busily learning new stuff.
I like the clarity changing that wording would provide, and putting a "why" behind it...
Thanks
|
|
|
|
|
Personally, I'd move #4 & #5 into a tie above the current #3 but that's just me...
Contrary to popular belief, nobody owes you anything.
|
|
|
|