Heading back to 2009 – JUST A DEVELOPER????!!!!
I looked back at my old blogs – and think about all there is to write about now! There are many, many, running through my head. There just isn’t enough time in the day!
What has changed? We could count the ways. But let’s not. There really haven’t been any radical changes. We have more development tools at our disposal. We have to be knowledgeable about what is available and when we should use it. Oh, so I said I had to be knowledgeable. Did I say that out loud? Silly me.
The real world, there are some, not all, people that feel the business analyst not the developer should determine what development tool to use when. Let’s repeat the title B-U-S-I-N-E-S-S analyst. Now would I go tell the business analyst that she should be configuring field xyz different, and maybe this should be master data instead of configuration? NO! Why? Because although I have limited knowledge of configuration. Do I have knowledge? Duh. Yes. We have to be knowledgeable to develop with SAP instead of against it. So although I have limited configuration knowledge, I know that 99 times out of a 100, the business analyst will configure the solution better than I. That one time, I’ll ask about why she did what.
But the reverse! The reverse thinking is not true. Will the analyst who knows a little or a lot about what is out there will simply debate or suggest what to use? No they will do the actual T-E-C-H-N-I-C-A-L design. Really? What a strange world I live in. I keep looking around for the cameras and the person to say “Smile you are on candid camera”. (An old TV show where there was a joke being played on the person.)
So what makes you think you know enough about development to tell us exactly what to use when? Why don’t we talk about it. I may have some tricks you don’t even know about!
You want to design really? Even if we let you do the technical design, why would you have to know about the business functions / processes? Why do they want to be included in the functional design? We really don’t need them there. We know enough about the technology and the business to write excellent specifications. All the developer has to do is follow the specifications! If they were any good and wanted to design they would change jobs and be a business analyst!
h3. Hold on for a ride!
I can already tell this blog is going to go round and round in circles – so if you are going to read all this, hold on your going for a long ride!
h3. Development is fun! Maybe? Sometimes? Really?
I LOVE to develop. I LOVE to work with the business and help develop the solution. And – little print here – I love to know the process. I love to know how my little piece fits into the whole.
My enjoyment is, yes, the final product. I love to know the final product is being used. But like everyone else I’m human. I want to be involved in the design of the final product. It’s hard to keep hearing “the dime a dozen programmer” comment. Why? Because then it sounds as if anyone could do my job. I want to think that not everyone could do my job. And I KNOW not everyone could do my job. So, hey, knock, knock – WAKE Up! I’ll stand up on a chair. Can you see me NOW? I am a person and not a mindless drone. NOT EVERYONE CAN DO MY JOB. Or your job if you are a developer. If you are a Taxi driver , I sure couldn’t do your job.
* A*nd that’s the whole problem! Now and with my last rant! Remember Developer’s are a dime a dozen. They obviously could never understand the functional side. Shoot we may not even need them. About ‘Embracing Inclusion to Drive Innovation’. And if the developer is any good their not a developer anymore they’ve moved to a different job. Right?SO – Receiving Poor Feedback – does this make me whiny. Another blog I’ve read recently. Or does that make me a “would-be” agent of change? I guess it depends on which side of the argument you are on.
Did you read my Just a developer?!? Does this one sound more subdued? Yes, this time it is. I have been in a lot of areas where functionally I have no idea what is going on. I have learned the value of having that functional person. I am knee deep in new technology and new ideas. I still keep up with my “old” process areas. I’m too curious not to. And someday, well, someday hopefully, I’ll get to do a project in on of them. I guess that could be bad if I ended up with a non-cool functional person. We would clash a lot and that just isn’t good.
If you got all the way down here! Oh my Gosh! You are good. It’s all way too long for one blog. But it all fell into one blog. So there you have it. The person that writes long comments. WRITES HUGE BLOGs – but only sometimes!