This year Apiumhub partnered up with Coding Sans and other software related companies like InstabugClutchShippableCode GiantStrideCodeshipUsersnapGitKraken, and took part in global software development research to find out how companies attract software developers, what are the most popular languages, what are the most frequent challenges, etc. We got more than 300 answers from different countries around the world and we really hope that you will find this report interesting. To get the full report with Interesting facts about software development, click here.

Sneak Peek: Interesting Facts About Software Development

And now, let’s look at some of the data from the report to get an idea of what to expect from this report. Let me highlight that in this article you won’t find a detailed explanation of each graph and question. It is just a sneak peek.

Source de l’article sur DZone (Agile)

One of the most common critiques about Scrum that I’ve heard from smart software engineers is that "Scrum does not care about technical practices. Scrum is for wimps." I’ve also heard managers down the hallway say that "Scrum is for wreckless developers because its main concern is only about fast delivery." I’ve heard many business analysts and solution architects tell me that "Scrum is too fragile because it does not specify the documentation the team needs to write."

People often say these things because they could not find in the Scrum Guide that says what technical practices the Scrum team need to do. But just because the Scrum Guide does not explicitly mention any technical practices you need to do, it doesn’t mean you couldn’t or shouldn’t do any technical practices. In fact, professional Scrum teams will find that technical practices are required for the software to be sustained in the long run. This is what agility is all about, not just about being fast in the beginning but slow at the end because of technical debts.

Source de l’article sur DZone (Agile)


Agile – Roots and Current State

When the concept of Agile delivery was originally designed, it primarily focused on improving software development for small teams where nimbleness and efficiency were more easily attainable. However, with the spread of Agile in the software development community, more large enterprises desired to gain the efficiency and speed associated with Agile teams. Unfortunately for large enterprises, staying nimble and flexible while delivering code is difficult with all the established bureaucracy. However, as Agile has matured it has provided a method for large enterprises to maintain nimbleness and speed for delivering code.

To understand how Agile can improve software delivery for large enterprises, it’s important to understand traditional project management and how it differs from Agile. Most large enterprises use traditional project management guidelines due to strict constraints associated with their projects, which usually impact the entire enterprise. They use these constraints in an attempt to maintain quality in the product they are delivering. These three constraints are the following:

Source de l’article sur DZone (Agile)

Last month, we were very fortunate to have André Meyer come into Tasktop to give a presentation on fostering software developer productivity. For many years André has been working with a research team with one of our company co-founders, Gail Murphy, to address the ongoing supply and demand shortage in software delivery.

As "software continues to eat the world," the need for software is outstripping our ability to supply it. Just how do we enable and empower software developers to build better software faster and make them more productive?

Source de l’article sur DZone (Agile)

Before explaining a sprint retrospective, I am assuming that you have a fairly good knowledge of Agile practice management. This blog doesn’t cover Agile basics. This blog is for anyone who wants to be successful in running an Agile Retrospective.

The sprint retrospective is just for Scrum teams and gives the team an opportunity at the end of the sprint to take a look back at the sprint that just ended, which may be one or two weeks depending on your sprint length and determine, what went well, what problem areas that may have had and how they can improve upon those areas as they move forward to the next sprint.

Source de l’article sur DZone (Agile)


You

Introduction

Do you love your job? I am sure that you have thought of this question before, or perhaps someone might have asked you this question. I agree that it is a simple question, and it has simple words in it. But were you able to answer that? If you have never tried to answer that, please try now. If you have a satisfying answer within you, then that is amazing. Unfortunately, if you can’t answer that positively or are uncertain, please read this post.

Background

If you want to see some tips to become a successful software engineer, I strongly recommend that you read my post here. Until now, I’ve worked with many companies, including startups and multinational companies. After joining a company, I asked this question “Do I love this job?”, “Is it what I am capable of?”, and “Is this work challenging me?” Sometimes, the answer to these questions came in the form of my resignations. In this 7-year span, I have learned a few things, and I am happy to share that information with you all. You can always see the articles related to career advice here.

Source de l’article sur DZone (Agile)

One of the main selling points of open plan offices is that they are good for collaboration. Their ability to support ease of communication among employees is supposed to encourage teams to work effectively together. This is then supposed to offset their damage to individual work that requires high levels of concentration.

Except the evidence is mounting that they aren’t even that good for supporting collaboration. Earlier this year a study from Karlstad University, Sweden found that open-plan office spaces not only harm collaboration, but also reduce employee happiness.

Source de l’article sur DZone (Agile)

If you’re like me, every article you’ve ever read about managers vs. leaders bagged on managers while praising leaders. Not surprising, right? People hate being "managed" and nearly everyone fancies themselves as being (or becoming) a leader. 

There may come a time when managers are obsolete, but for now, these are both valuable roles – they’re just different.

Source de l’article sur DZone (Agile)

Anyone who touches product development knows all too well the importance of QA. But what about those at the executive level?

CIOs and CTOs might have different priorities than their product development teams, but at the end of the day they should care about testing just as much as everyone who touches the software. That’s because properly managed testing — meaning testing that’s consistent, repeatable and occurs early and often — can actually speed time to market and prevent buggy software. As a result, the right testing strategy can increase revenue, drive innovation and prevent costly mistakes.

Source de l’article sur DZONE

dcipher – Online Hash Cracking Using Rainbow & Lookup Tables

dcipher is a JavaScript-based online hash cracking tool to decipher hashes using online rainbow & lookup table attack services.

The capacity to programmatically crack passwords is also a function of the number of possible passwords per second which can be checked. If a hash of the target password is available to the attacker, this number can be in the billions or trillions per second, since an offline attack is possible.

In this case dcipher uses online hash checking services, which have extremely large Rainbow Table sets of pre-computed hashes, to rapidly find hash collisions.

Read the rest of dcipher – Online Hash Cracking Using Rainbow & Lookup Tables now! Only available at Darknet.

Source de l’article sur Darknet