Every week here and in our newsletter, we feature a new developer/blogger from the DZone community to catch up and find out what he or she is working on now and what's coming next. This week we're talking to Ajitesh Kumar, Principal Architect with Evoke Technologies.
The real reason the Theory of Constraints remains a statistical game in networking has nothing to do with technology. The reality is that once anyone grows accustomed to solving a problem in a particular way, they use that method to solve it over and over again.
I've recently been looking at retrofitting keyboard navigation support to JS Bin, but I was immediately struck by the totally lack of visibility on what was in focus. So I built a mini utility to visualise what's happening.
This article will explain how to debug Gradle plugins in IDEA without remote debug, just like a normal Java application.
While Story Mapping goes a long way towards identifying the work that needs to be completed to deliver a viable system, you will inevitably miss some stories. This is a natural outcome of the discovery process that is inherent to software development.
I’ve read many times about teams that adopt a ‘sledgehammer to crush a nut’ approach and trust me, it works. This is not the how of such sessions, just the way in which I track them for the team. If you have a big ol’ nasty nut that you intend to crush in one session, then I hope this little technique helps.
Businesses will need to adopt better network security measures alongside their device initiatives. One of the best ways a business can prepare for future issues is to create rules and guidelines for how to handle new devices.
I'm not even certain that I could help them with some of the Python technology required to extend scipy. But, I'm sure I cannot actually do anything of value under the circumstances that (a) they have not really tried the established algorithms and (b) they're already sure that the established algorithms can't work based on religious-wars arguments.
Release externally whenever you want. That is a business decision. Separate that business decision from your ability to release internally all the time.
TL;DR: The realities of modern corporate networks make the move to distributed database architectures inevitable. How do you leverage the stability and security of traditional relational database designs while making the transition to distributed environments? One key consideration is to ensure your cloud databases are scalable enough to deliver the technology's cost and performance benefits.
Following up on my Why We Need to Teach Kid to Code, here are some fun ways to help them learn. So cool – wish some of these were around when I was an 8 year old learning to code on my Atari 800!
Should we design cost-effective disposable software?
The existence of silos in large companies is fairly common. But simply knowing that silos exist doesn’t help too much. The operable question for everyone operating in these environments is: What can I do to remove unnecessary silos?
Industries have accepted ERM software in their work space and have analysed and calculated its constructive and destructive roles. Implementing a wrong, defective or inadequate program has contributed to the failure of countable enterprises.
In the meantime it seems to me that a lot of the problem with Estimates lies in what they are, what they are not, how they are used and how they are mis-used.
For me recruiting a programmer has to start with code. I don’t really care about the CV and the application process for this job involved a quick coding problem.
These two bind command change the way that the up and down arrow keys work once you start typing a command to only search the history for lines that start with what you've typed so far. It's quite handy and I find it easier to use than ctrl+r.
Look, the more people and teams on your program, the more feedback you need. The more chances you have for getting stuck, being in the death spiral of slowing inertia. What you want is to gain momentum.
Agile is a methodology that was formed to bridge the gap between abstract requirement and real-world want. It implicitly acknowledges the existence of the gap by requiring the business to participate and therefore to be complicit in the process of development and delivery. It is the best methodology I have ever seen for overcoming this problem and this problem is the single biggest cause of pain in software development.
Companies are not blind because the individuals are not talented; they are blind because there are powerful psychological dynamics at play that keep us all from seeing that which we must see the most.