|
|
Congrats!!Keep up the good work!!!
|
|
|
|
|
Congrats!
The signature is in building process.. Please wait...
|
|
|
|
|
Congratulations, Sri Sandeep,
Here on CodeProject there are great differences between individuals in terms of talent, experience, skill, technical mastery, and the ability to be articulate in the English language which is required to be used here, but, we are all part of a community of people who can learn from each other, teach each other, and help each other improve.
As community, we will never be "perfect," or have "perfect justice;" and, all the negative imperfections of the human condition will be manifested here, sometimes amplified in intensity by the somewhat de-personalized technology that is our means of communication, but:
So much more wonderful than the inevitable "down-side" is the fact that such a community exists, and is a fabulous playground for the minds of millions of people, world-wide !
"Rahi gulzar to phool khilenge" Kabir
“But I don't want to go among mad people,” Alice remarked.
“Oh, you can't help that,” said the Cat: “we're all mad here. I'm mad. You're mad.”
“How do you know I'm mad?” said Alice.
“You must be," said the Cat, or you wouldn't have come here.” Lewis Carroll
|
|
|
|
|
Spend them wisely
You cant outrun the world, but there is no harm in getting a head start
Real stupidity beats artificial intelligence every time.
|
|
|
|
|
|
You ruined it by posting
|
|
|
|
|
Right up until you posted that message, thus making it 1112... rofl...
|
|
|
|
|
that's my next step to achieve 2,222!
Don't mind those people who say you're not HOT. At least you know you're COOL.
|
|
|
|
|
You're even closer now... You can thank me later!!
|
|
|
|
|
_Damian S_ wrote: You can thank me later!!
why not now?
thanks..
Don't mind those people who say you're not HOT. At least you know you're COOL.
|
|
|
|
|
|
What is that ?
a new web site ?
I'd rather be phishing!
|
|
|
|
|
Thank you Sherlock
Zen and the art of software maintenance : rm -rf *
Math is like love : a simple idea but it can get complicated.
|
|
|
|
|
I aim to please.
I'd rather be phishing!
|
|
|
|
|
have you test website crawler on Codeproject ?
Thanks
-Amit Gajjar
|
|
|
|
|
CM's new toy. It's development platform including - so far - a git machine and task manager, arranged into workspace. So of us - unfortunately got access to it to test and play. I believe that you also can - if there is more place. Ask for in the Bugs an Suggestions if you interested...
(It also became - slowly - the storage place for article's code...)
I'm not questioning your powers of observation; I'm merely remarking upon the paradox of asking a masked man who he is. (V)
|
|
|
|
|
I'm looking for advice on how to deal with a problematic stakeholder/boss. If your advice has anything to do with quitting or leaving, save your breath. I'm well aware of that option. I'm interested in hearing ways to salvage the project.
I joined a small business whose owner wanted to replace their failing DOS-based ERP with an ASP.NET solution. (Awesome, right?)
My boss, the owner, is a 60 yr old, stocky bulldog whose tenacity is at the core of his successful business. Around the office he has the reputation for being a meddlesome teddy-bear.
I am the only in-house developer. The biggest problem is that I can't seem to find a way to communicate with the owner. He has yelled at me multiple times for asking questions and drawing diagrams . He has shut down my attempts to understand the business, making it nearly impossible to put a game plan together. He doesn't understand the process of software development and constantly says things like, "Do we really need to do all that? Can't you just start with the first screen?"
"Sure - what do you want the first screen to do?"
"Exactly what it does right now?"
"But it doesn't really suit the way your staff does business."
"Well, we'll change the parts that don't work?"
"Ok - How? What parts don't work? How should-"
"Look we can just deal with that later. Let's just start building the first screen and go from there."
I tried to explain that I need to understand the processes that I'm trying to support before I can 'design a screen'. Exasperated, the owner grabbed a fresh-out-of-college graphic designer in marketing and told her that she would be designing the layout and workflow of the new app.
A few weeks later I received a mock-up of a giant page with a billion fields and no discernible purpose. The owner loved it. He stopped by and generously asked me if there was anything I'd change.
How would you turn this into a win?
Subversively talk to staff, build a plan in secret and slowly evolve the graphic artist's shotgun layout into the more appropriate design by pointing out flaws one at a time? Is it worth the effort?
Just wire it up like the owner wants and let the flaws become self-evident?
|
|
|
|
|
Well, the obvious thing to me is that the UI mockup won't be addressing edge cases - there's an education process that needs to be done here, so start off by working out what a couple of the edge cases are and asking how they would be addressed. One of the things I would address with him is the fact that a wrong design decision now will end up costing a lot more further down the line, and the processes you are following are designed to save him pain and money in the longer term.
As we don't know what the business is, we can't offer much in the way of advice - but there's probably something analogous in his business that he has to approach properly otherwise it will go "belly up" for him. In other words, relating things to him in a way that's familiar will make it much easier to sell it to him.
|
|
|
|
|
Thanks -- good food for thought. Teach and train. I see a lot of deep breaths ahead, but seeing this thing work will be very rewarding.
I like your suggestion about finding ways to relate to him. We are such completely different people... That's going to be tricky.
|
|
|
|
|
I regularly go through exercises like this with my clients. It's frustrating at first, but ultimately it's rewarding.
|
|
|
|
|
One of those edge cases must be mobile computing - can't put very much on a mobile screen before it starts looking pained...?
|
|
|
|
|
Agreed. That is on the list :/
|
|
|
|
|
If you honestly want to salvage the situation you will have to become an educator.
Teach the designer how to design. The the staff how to communicate their needs to the designer (teach them how critical this is to their future). Teach the boss how to understand your needs.
Make sure things are very iterative and goals/milestones are easily reached and reviewed frequently (buzzword - agile).
Make sure your communication is very simple and to the point (nobody seems to want or is capable of details). Only ask questions that require simple answers.
Also, one last thing... communicate to him there are two kinds of knowledge you need as a developer:
1. Technical knowledge (which he is paying you for)
2. Domain/Business knowledge (which makes your tech skills more valuable to him as you can work more effectively)
Domain/Business knowledge are things like "defense industry", or "medical IT", or "Retail and Point of Sale". Developers with the appropriate domain knowledge are critical for closing the gap when the business analist is missing or misses details.
|
|
|
|
|
Excellent response. Thank you.
|
|
|
|