For startups and small businesses, it’s crucial to start using special project management tools early on. However, the price of most tools is barely affordable for a new business. The good news is that a tool with all the necessary functionalities can be cost-efficient! Here is a list of free project management software tools that are great to start working on your projects with.

1. GanttProject

GanttProject allows you to organize work structure and manage projects in an easy way. Create tasks and break work down in a hierarchical tree, set deadlines, priorities, and milestones, and create dependency constraints between tasks. Set up profiles for system users with basic contact information, pay rates, and roles. Assign them work and monitor their workload.

Source de l’article sur DZONE

This article was originally written by Joff Redfern.

When we announced Stride in September 2017, we said, “It’s time we rethink the way we’re working. We believe that teams can stay connected and keep moving forward.” We still believe that. We knew we were taking a risk by entering an already competitive real-time team communications market, but we were willing to do the hard work necessary to build a great product. And we believe we were on that path. Stride was a bold project, and we’re very proud of the product we created and the team that created it.

Source de l’article sur DZONE

Co-working spaces are booming, with some 2.5m sq ft of co-working space in London alone at the moment. That’s an increase of 190% in the last year. Whilst the rise in the gig economy is an undeniable factor in this trend, there is also the promise of co-working providers that working in their facilities will make your work more creative and more effective. Great effort is put into designing spaces that are built to support innovation.

It’s a concept that has a lot to rationally support it. There is a strong need for flexible workspaces, and most facilities do look like superb places to plug into and work. Do they actually deliver on their promise though? Is the hype in the marketing material matched by reality on the ground? That was the question recently posed in a new paper by Creative Friction and the London School of Economics.

Source de l’article sur DZone (Agile)

In the days before web applications, programmers wrote applications for a specific platform and used that platform’s native development environment and user interface controls. Before the application’s final release, a tester would check that the application was ready. Some testers wrote elaborate documents that described complicated scenarios they performed on the software manually. Other, more adventurous, testers used fancy tools that were the quality assurance version of Microsoft’s Word and Excel macro recorders. A tester would record a series of actions on the software under test. These steps were recorded in a high-level language in which the tester could edit the code and add test conditions that would verify that the actual results of the test matched the expected results. Each time a test was run, a report was generated that showed which conditions had been passed or failed.

With web applications, the time it takes to write and deploy code has been reduced to seconds. In this environment, much of the responsibility for testing is now in the hands of developers, who have since created many code-based test automation platforms.

Source de l’article sur DZONE

It all started when software development teams were physically present in the same office and interacting with each other face-to-face. At that time, this was thought to be the best way to get work done. Not many employees worked remotely. But, that era is long gone. By comparison, most of the organizations today have distributed teams. They ease the burden on project infrastructure and improve the employee’s comfort level.

A good infrastructure cannot have the dependency on only one system or person. Infrastructure needs to be distributed to avoid SPOF (Single Point of Failure). Similarly, it makes more sense to have distributed teams. This helps in a DR (Disaster Recovery) situation and also in hiring talented people without the time or location constraints.

Source de l’article sur DZone (Agile)

As mentioned in the previous article, Vert.x is an event-driven, non-blocking toolkit. It was designed for asynchronous communications. In most cases, you need to work with multiple verticles in your applications. You also need communication between these verticles in these cases. In this article, I will attempt to explain how you can do this — let’s get started!

Use of Multiple Verticles

An important note to remember is that a verticle is a unit of deployment. It allows you to encapsulate your code for different needs. In addition, they can be run independently of each other. Verticles are communicated with each other by sending messages on the event bus. For this example, we have developed two verticles. One is the sender and the other is the receiver. You can access code for this example from this repository. The start method in the SenderVerticle class is as follows:

Source de l’article sur DZONE

The freedom and flexibility to work on your own terms add to employees’ happiness. Technology and the internet have made working from home possible for many employees. This option not only eliminates the need for travel, but also offers more flexibility.

Some companies still believe that employees are more productive in the office, a notion challenged by many companies today; some firms are going 100% remote with a distributed team. Even without a physical office, they achieve productivity and success.

Source de l’article sur DZone (Agile)

In this blog post, we will follow up the "Linux Namespaces and Go Don’t Mix" post, and we will show how the problem mentioned in the previous post was resolved in the recent release of Go 1.10.

Problem

To recap, the main problem was that the Go runtime did not allow us to safely change a local state of an OS thread ("M" in the Go notation) scheduling a goroutine, even if the thread had been locked with runtime.LockOSThread.

Source de l’article sur DZONE

Whether you are doing an IT audit, or you are a new CIO in your company, you must quickly take a good vision of the situation of your IT. What are the strengths of your IT? Areas for improvement? And especially in relation to your business context, how does IT do its job properly, in terms of business satisfaction, cost control, the speed of implementation, and a low number of incidents to manage?

Business Strategy

Do Big Changes Occur Often and Quickly or Not?

There is no point in having a very Agile IT if you evolve once a year. In the opposite, it is useless to have an IT that can’t move if you have a lot of evolutions. You see the point?

Source de l’article sur DZone (Agile)

It’s about time that you reconsider Java as your go-to language for your Android-based projects. And, it’s about time to switch over to Kotlin, the (not so) new support language for Android development. But, what’s behind its surging popularity amongst developers? In other words, what are the biggest advantages of Kotlin over Java?

Why should you even consider trying it as an alternative to the sometimes problematic, yet familiar and reliable Java? Now, here are some of the best answers to your questions:

Source de l’article sur DZONE