Closed. This question is off-topic. It is not currently accepting answers.
Want to improve this question? Update the question so it's on-topic for Stack Overflow.
Closed 11 years ago.
Improve this question
As part of my assignment, I am supposed to find out what would users like to do while they're waiting in line (for anything).
I would appreciate if you guys could provide your input.
Any time you give users something to do while your process is working, you risk massively alienating all of them. In my experience, users hate waiting entertainment especially if it creates the feeling that it might extend the actual waiting.
The very best thing to do in this situation IMO is to tell the users exactly how much longer they will have to wait so they can fill the time productively on their own.
They may get their cellphones or smartphones to play games, browse
on mobile internet, watch mobile TV, do SMS or call their friends.
There are others with newspapers and books and read these while they are in line.
Others might be daydreaming.
There are people busy listening to music.
If they have companions, they are going to chat with them.
Part of your assignment in what? What does this have to do with programming? Do you intend to program the people in line? If so, I recommend the Clockwork Orange approach, complete with the 9th.
Related
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 3 years ago.
Improve this question
I can't say I'm weak in programming but I can't come up with the logic faster. I can analyse others code and get to know the logic. But I can't do it on my own. How can I improve my programming skills?
Quite a broad question but from my own, 30yr experience I can tell you there is no way around starting to
analyze existing code,
modify some things (play with it until it feels like it's your own code)
see what the changes do
develop your own ideas on how to do things faster/better/more beautiful
implement your ideas
see if it works
go on to more complex tasks
read books (very important, because many things can't just be discovered by trial'n'error)
be very passionate and determined about what you want to become reality
if you want to learn faster, then write more code
One very important item. You should have fun with what you do is always the best guarantee for success
If you fail at these items then I'm afraid you will never succeed with programming. But then maybe it's like any other field of knowledge.
I experience the same difficulties during my learning journey, too. When I complete challenge tasks I create more complex tasks for myself to see what I can do. It takes me to the next levels of solving problems.
Practice, Practice, Practice!
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 7 years ago.
Improve this question
I have 5 apps that I want to make right now, but creating them one by one seems inefficient. It seems like a better idea to make them all at approximately the same time in order to share segments of code where applicable. What are your thoughts on the most productive way to create a long list of moderately complex apps? For comparison, let's put them all on the difficulty level of a familiar & simple app - SnapChat.
Even though it sounds more efficient this sounds like a surefire way to either at best waste time or at worst (and most likely) get a lot of half written apps that never get to production. Unless this is a white label app where instead of 5 separate apps there is one app with 5 different skins you will likely never finish one of them let alone five. A 'simple app' like Snapchat still requires a lot of development time and testing, user adoption studies, and most of all focus of your effort.
Based on your question you have a good deal to learn about the development process. That is fine, you can do it, but focus on the best idea and put all your effort into that. It will take a lot more time and work than you expect and you will be happy you aren't worried about four other projects.
Closed. This question is off-topic. It is not currently accepting answers.
Want to improve this question? Update the question so it's on-topic for Stack Overflow.
Closed 11 years ago.
Improve this question
Are there some good alternatives for a Nabaztag? We want to get several of these, but they're not cheap.
Some alternatives:
Lava Lamps
Ambiant Orbs
The mentioned Tux droid
A build dashboard on a monitor or LDC (like Hudson's Radiator View or eXtreme Feedback Panel)
Also check the following questions:
What’s your Favorite Extreme Feedback Device?
Any experience with a Continuous Integration Appliance?
please recommend an easy to setup device for visually indicating Build Status
Bunnies, a build dashboard, Lava Lamps, they'll all do the job. But racing against the wax of lava lamps (as mentioned in one of the question above) is indeed fun :)
the tux droid might be a good alternative: http://www.kysoh.com/
last time i checked it cost about half the price of a nabaztag.
Just put our Parabuild's build dashboard on a large LCD TV in the hallway and you will get a nice build radiator.
Depends on what you want to use it for and how you want it to look. But the Insignia™ - Infocast 3.5" Internet Media Display is down to $50. It's based on the Chumby (another option to consider) and is software and hardware hackable. Info on the hardware is at http://www.bunniestudios.com/blog/?p=1140
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 3 years ago.
Improve this question
Someone within my organization has started pushing for us to pilot the CMU SEI's TSP process (see website here). I have an instinctual aversion to any attempts to cure software development illnesses with alphabet soup, but I would like to know if anyone has experience with this process and can provide tangible facts.
I used to be a fan of SEI's CMM. I even read Watts Humphrey's "Managing the Software Process" book cover to cover. I haven't used TSP but I suspect it has similar strenghts and weaknesses as the other software processes.
Definitely read about it and what they claim it can do and how to implement it, but be vigilant about keeping your software process small and flexible. You need one, but be careful about taking processes from someone else.
good luck.
We've been using this process for a few months now and I'm not particularly impressed. This process is only suitable for a strict command and control style of management where programmers are essentially bean counters. Most of the good parts of this process (size estimates rather than time estimates, self reviews, detailed plans, logging time against plans, and keeping a log of defects and errors for later review) can be implemented without throwing a bunch of money at SEI.
Closed. This question is off-topic. It is not currently accepting answers.
Want to improve this question? Update the question so it's on-topic for Stack Overflow.
Closed 10 years ago.
Improve this question
I've read a long time ago an article about why managers should appreciate the devs., and there was analogy drawn to the 7 samurais movie: that a company can't really offer much to an engineer, and that the engineer chooses to help the company -- like the samurais helped the villagers.
I thought that was on joelonsoftware.com, or codinghorror.com; but the search did not bring any result. Does it ring a bell to anyone? Anyone?
It's from Joel's book "Smart and Gets Things Done". Section is entitled "Treat Them Like Samurai".
A quote:
The village is your team. The samurai are the programmers who, you hope, will come solve your problems, bringing their talent and expertise in exchange for, maybe, a bowl of rice. You may be poor and hopeless, but you sure as heck know how to show some respect for the samurai who is going to save your behind.
Nothing about Samurai, but another 3 articles from Joel that relate to management/developer relations.
Field Guide to Developers
Development Abstraction Layer
Two Stories