The Lounge is rated PG. If you're about to post something you wouldn't want your
kid sister to read then don't post it. No flame wars, no abusive conduct, no programming
questions and please don't post ads.
Not only do I not have facebook on any pc, I have actively tried to get rid of it from my phone (which I have concluded, is impossible without rooting it, and even then I ma not sure it would get rid of it, its like some horrible std)
You cant outrun the world, but there is no harm in getting a head start
Real stupidity beats artificial intelligence every time.
On Windows Phone 8 (Lumia 720), when you switch to silent mode, videos play with sound and some apps emit sound. Why are the individual apps expected to check the silent status and behave themselves accordingly? Why can't the OS force the silent mode so the speaker goes absolutely silent no matter what? I think that is how Android behaves. Any thoughts?
I dunno about Android: if I turn the volume to Mute, the alarm still sounds at "normal" volume - it's independent of the "standard" volume control which affects video, music and email chimes.
It's what you want I think, but...it isn't "mute" as such.
Those who fail to learn history are doomed to repeat it. --- George Santayana (December 16, 1863 – September 26, 1952)
Those who fail to clear history are doomed to explain it. --- OriginalGriff (February 24, 1959 – ∞)
Anything that is unrelated to elephants is irrelephant Anonymous ----- The problem with quotes on the internet is that you can never tell if they're genuine Winston Churchill, 1944 ----- I'd just like a chance to prove that money can't make me happy. Me, all the time
I have got 10K reputation point on CP. Thanks to all who motivate me and support me. I also want to give thanks to each code project member who voted my article/tip/Forum answer that thing motivate to me write best.I want to deliver my best here in easy way via Article, Tip and Forum. I am enjoying here and hope same from your end. Again Thanks.
I am <layer>enjoying here and hope same from your end
The same goes to me, too. In this forum, I can proudly say that "programmers/developers have no life" thing is not true!
Programmers/developers live in an awesome life. No one would ever know it unless they are like us.
Don't mind those people who say you're not HOT. At least you know you're COOL.
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
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.
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.
"We can develop the code for the first screen as the designer has shown and then spend time to modify it for the changes that we know we'll need, OR
we can spend some time up front to figure out exactly what we really want it to do and then develop that.
The second way is almost certainly going to cost less!
I admit, the second way will feel like we're not making any progress for awhile, but knowing what we're actually aiming for means we won't be wasting time and money working on the parts we'll change anyway."
Last Visit: 31-Dec-99 18:00 Last Update: 27-Jun-17 18:09