|
He he! Luckily I'm doing ASP.NET/C#. Sometimes I just start talking to my colleagues about some dev-related topic. They usually make a puzzled face and keep working. 
If you truly believe you need to pick a mobile phone that "says something" about your personality, don't bother. You don't have a personality. A mental illness, maybe - but not a personality. - Charlie Brooker
My Blog - My Photos - ScrewTurn Wiki
|
|
|
|
|
It's GREAT being the only developer! I don't have to struggle to understand and patch someone's incompetently-written framework. Everything's done the RIGHT way, everything's commented, and I understand the whole system.
At other jobs, I had to struggle to understand undocumented classes, 400-line methods, idiotic algorithms and variable names, and unreliable code, which made me look as bad as my predecessors. Now everything just works.
Other programmers often just cause problems and get in the way.
|
|
|
|
|
Alan Balkany wrote: Everything's done the RIGHT way
But who decides what is the right way?
If you truly believe you need to pick a mobile phone that "says something" about your personality, don't bother. You don't have a personality. A mental illness, maybe - but not a personality. - Charlie Brooker
My Blog - My Photos - ScrewTurn Wiki
|
|
|
|
|
Good question! Working alone person can reach some point in skills and then stop self development at all. And sometimes when you've developed your own framework and you proud of it - it happens that your "child" looks like a bu***it comparing to another framework. It happens. So I think if you work alone - you can't say that something you do is perfect until it is confirmed by another same or more skilled developers.
------------------------------------------------------------
Want to be happy - do what you like!
|
|
|
|
|
In '92 I graduated University and, at that time, I lived a small town. While I was writing my licence thesys I realised that probably, 30 miles around I was the only able to write a C program. That time I was very proud. In fact it is very sad ...
36. When you surround an army, leave an outlet free.
...
Do not press a desperate foe too hard.
SUN-TZU - Art of War
|
|
|
|
|
I worked for myself some years and I too discovered that it works better if you have one or more developers besides you on a team. It tends to make work easier and also the quality is going up as the other developers correct wrong ideas and extend good ideas you have.
Of course there are downsides to working with a team, like the need to clean up the mess that others left behind. But that's all part of the job and the pros outweigh the cons here.
WM.
What about weapons of mass-construction?
"What? Its an Apple MacBook Pro. They are sexy!" - Paul Watson
My blog
|
|
|
|
|
get me a job there buddy 
|
|
|
|
|
Ditto that - I'm the Architect, Developer, Documentation Writer, QA/QC department, while from time to time I'm also the database admin, the support guy, and the magic fraking 8 ball. I am always introduced by my employer to others as the Development Manager/Team Leader, to put them off the scent that the only team is in fact just me, myself and I..
While this has it's advantages when it comes to product direction (no-one to debate architecture with) and QC (no-one's bad code to debug), it definately has its disadvantages when it comes to milestones and deadlines. Unfortunately the boss often forgets that if I spend half my day answering emails, there's only half a day left for coding. He also tends to dismiss feature creep as something that might impact my productivity and timeliness of deliverables.
Come to think of it, I'd much prefer to be a part of a team. The one man band thing sucks. I need a new gig.
|
|
|
|
|
|
But lately I've been thinking that janitorial work is a lot more rewarding. 
Marc
|
|
|
|
|
Not necessarily[^]; it depends upon the type and grade of, er, muck you have to clean up.
Software Zen: delete this;
|
|
|
|
|
|
I work in infrastructure, but i'm not a manager... so not sure what i would be described as... i guess the best answer would be clistctrl
|
|
|
|
|
StevenWalsh wrote: clistctrl
|
|
|
|
|
come on... its a codeproject tradition (at least when theres a fill in the blank slot) to put clistctrl as one of the answers 
|
|
|
|
|
|
Of course! CListCtrl is a suitable answer for all questions! It is even more accurate than answering "42".
In fact, you can answer arbitrary questions with CListCtrl. E.g.:
Q: "Do you love me?"
A: "CListCtrl"
Q: "What time is it?"
A: "CListCtrl"
Q: "My hovercraft is full of eels?"
A: "CListCtrl"
And, of course
Q: "How to display a list of data with icons in MFC?"
A: "CListCtrl"
|
|
|
|
|
Uwe Keim wrote: My hovercraft is full of eels?"
[Insert Witty Sig Here]
|
|
|
|
|
... given that I have all of the departmental sh!t jobs: I write the installers for our products, I write all of the public-facing documentation (public means the rest of the company), I keep the build machine and our automated build process working, plus I'm the SourceSafe data base administrator/guru/guy-with-the-plunger-when-the-DB-gets-scrogged  .
Software Zen: delete this;
|
|
|
|
|
I find the choices limited...
I decide what we need, design it, build it, program it if it needs programming, and fix it if it's broke. Who needs specialists?;P
"A Journey of a Thousand Rest Stops Begins with a Single Movement"
|
|
|
|
|
but an "architect" is some one who designs houses. I would never describe myself as that, I don't need the ego trip 
|
|
|
|
|
ed welch wrote: an "architect" is some one who designs houses
Amen. My father is an architect and he doesn't know anything about software development.
Well, most "software architects" don't either 
|
|
|
|
|
Nemanja Trifunovic wrote: Well, most "software architects" don't either
|
|
|
|
|
I am developer/architect by poll. I research new algorithms, design software, and impliment the design by writing code. Since I am in an R&D field it is hard to split these since I have to develop the algorithm before I code it, which sometimes takes a long time depending on the new capability needed. So months I am primarily an architect, some months primarily a developer. Even asking for a majority is difficult. But I put developer mostly because I would rather not be considered ONLY an architect.
_________________________
Asu no koto o ieba, tenjo de nezumi ga warau.
Talk about things of tomorrow and the mice in the ceiling laugh. (Japanese Proverb)
|
|
|
|
|
I guess they should have had an analyst option :p
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
