Nabaztag alternatives? [closed] - continuous-integration

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

Related

How is UI Evaluated? [closed]

Closed. This question needs details or clarity. It is not currently accepting answers.
Want to improve this question? Add details and clarify the problem by editing this post.
Closed 4 years ago.
Improve this question
I am new to software engineering and also I like to learn whatever new. I must be very thankful if someone help me to provide further information about How is a UI evaluated?.
Any help regarding to this matter is highly appreciated.
In common, evaluation of User Interface can be based on three common elements
• Functionality
• Aesthetics
• Performance
Functionality
Is the application usable?
Does it enable users to complete tasks?
Aesthetics
Style
How it influencing the users
How shown and presented?
How colors complement each other?
How UI elements convey their meaning?
Performance
Measured not only by speed, but also reliability.
Reliability (Even though an application looks good and feels great, crashes repeatedly, it likely won’t be very successful)
Should provide a user with full confidence.

Is there some reliable way of detecting fake Facebook profiles [closed]

Closed. This question needs to be more focused. It is not currently accepting answers.
Want to improve this question? Update the question so it focuses on one problem only by editing this post.
Closed 9 years ago.
Improve this question
I believe this could be interesting for many Facebook developers. Is there some reliable way of detecting fake profiles on Facebook? I am developing some games and applications for Facebook and have some virtual goods for sale. If player wants to play more he can create another profile or many others and play as much as he like. The idea here is to somehow detect this and stop them from doing so.
Best Regards!
Put validation on no. of friends.. if no. of friends < A PARTICULAR THRESHOLD, disallow user, else continue. Well.. That's only an opinion, not a solution.. :)
You can try using anomaly detection.
Make your 'features' number of likes/spam/friends/other relevant features you've found helpful, and use the algorithm to detect the anomalies.
Another approach could be supervised learning - but will require a labeled set of examples of "fake" and "real" users. The 'features' will be similar to these for anomaly detection.
Train your learning algorithm using the labeled set (usually referred as training set), and use the resulting classifier to decide if a new user is fake or not.
Some algorithms you can use are SVM, C4.5, KNN, Naive Bayes.
You can evaluate results for both methods using cross-validation (this requires a training set, of course)
If you want to learn more about machine learning approaches, I recommend taking the webcourse at coursera.

Human computer interaction - waiting in line [closed]

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.

Do you have any opinions of SEI's Team Software Process? [closed]

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.

What is the best practice for estimating required time for development of the SDLC phases? [closed]

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 4 years ago.
Improve this question
As a project manager, you are required to organize time so that the project meets a deadline.
Is there some sort of equations to use for estimating how long the development will take?
let's say the database
time = sql storedprocedures * tables manipulated or something similar
Or are you just stuck having to get the experience to get adequate estimations?
As project manager you have to remember that the best you will ever we be able to do on your own is give your best guess as to how long a given project will take. How accurate you are. depends on your experience and the scope of the project.
The only way I know of to get a reasonably accurate estimate that is it to break the project into individual tasks and get the developer who will be doing the actual work to put an estimate on each task. You can then use an evidence based algorithm that takes the estimation accuracy of each developer into account to give you the probability of hitting a given deadline.
If the probability is too low, you have two choices: remove features or move the deadline.
Further reading:
http://www.joelonsoftware.com/items/2007/10/26.html
http://www.wordyard.com/2007/10/11/evidence-based-scheduling/
http://en.wikipedia.org/wiki/Monte_Carlo_method
There's no set formula out there that I've seen that would really work. Fogbugz has its monte carlo simulator which has somewhat of a concept for this, but really, experience is going to be your best point of reference. Every developer and every project will be different!
There will be such a formula as soon as computers can start generating all code themselves. Until then you are stuck with human developers who all have different levels of skill and development speed.

Resources