The trends in software development are showing that more and more companies are adopting CI/CD methodologies to deliver their software applications. We all know that the market demands quicker releases. The days of waiting for months for new releases are gone. Software is now being released at record speeds! Adopting CI/CD does just that. It helps get your application out the door to the market as often as possible. However, one key aspect that seems to be overlooked is Continuous Testing. It’s great that CI/CD is getting software out quicker but quality should not be sacrificed. To solve that you have to test early, test often! Adding a culture of Continuous Testing to your model will provide the following benefits because now you’re focused on testing from the beginning of your SDLC

  • Faster Release Cycles
  • Better Code Quality
  • Better Test Coverage
  • Better Reliability

Now that we know to truly have a CI/CD methodology you need continuous testing as well. But just like adopting CI/CD, continuous testing requires an organizational culture shift. So how do you build that culture? It’s a different mindset that relies heavily on automation: Automated Unit Tests, Automated Functional and Non-Functional Tests, Automated Regression Tests, and Automated Deployments. Basically, anything that can be automated should be automated! That is the key principle of Continuous Testing, test from the beginning and automate as much as possible to ensure faster release cycles.

Source de l’article sur DZONE

I am trying to develop a base API pricing formula for determining what my hard costs are for each API I’m publishing using Amazon RDS, EC2, and AWS API Gateway. I also have some APIs I am deploying using Amazon RDS, Lambda, and AWS API Gateway, but for now I want to get a default base for determining what operating my APIs will cost me, so I can mark up and reliably generate profit on top of the APIs I’m making available to my partners. AWS has all the data for me to figure out my hard costs, I just need a formula that helps me accurately determine what my AWS bill will be per API.

Math isn’t one of my strengths, so I’m going to have to break this down, and simmer on things for a while, before I will be able to come up with some sort of working formula. Here are my hard costs for what my AWS resources will cost me, for three APIs I have running currently in this stack:

Source de l’article sur DZONE

On this episode of Eat Sleep Code, Jen Looper and Diana Rodriguez discuss Vue Vixens, an organization of people who identify as women and who want to learn Vue.js to make websites and mobile apps. Jen and Diana share their story of creating and building a successful developer community and growing Vue Vixens into a worldwide organization.

You can listen to the entire show and catch past episodes on SoundCloud. Or just click below.

Source de l’article sur DZONE

This is a very frequent request that we come across.

“I have been a software developer for quite some time and would like to learn about a new role. I am excited about a business analysis career, but I have no idea as to how to transition into the new role. “

Source de l’article sur DZone (Agile)

Who is really building applications? The answer might surprise you.

In a survey of 350 non-professional developers, Forrester research found that a significant portion of employees were also contributing to custom application delivery, even when not considered to be IT professionals (How To Harness Citizen Developers To Expand Your AD&D Capacity, Forrester Research, Inc., April 19, 2017). Whether or not app development was part of these employees’ job descriptions didn’t stop them from seeking out these opportunities.

Source de l’article sur DZone (Agile)

I’ve been a conference speaker for 10 years; I’ve given many talks, been to many events, organized a few events, and now have Opinions (TM) about conference speaking. This tweet showed up in my feed when someone tweeted at me to thank me for my support in their talks.

Advice for conf speakers:

When someone you care for is speaking, sit in the first row. Be there for them. Laugh at their jokes, actually watch the talk (Twitter can wait), make yourself visible for them.

Be the audience you’d like to have, and next time you will have it.

Source de l’article sur DZone (Agile)

What is serverless? Serverless is a cloud computing model that was first introduced by AWS in 2014 (AWS Lambda is the market leader to this day). It abstracts away most of the server operations to the cloud provider so developers can only focus on writing code and shipping new features. Serverless adoption is rapidly growing and it’s mostly due to it’s promise of providing significant cost and time efficiency for technology companies.

For new startups, just starting to build their first product, it’s a no-brainer to build it on serverless. It’s very cheap and quick to get started. You don’t have to have that much knowledge about the backend processes, since the cloud providers handle all that and you can just focus on building your product and it’s functionality. The go-to-market time is much shorter than with previous computing models and it scales automatically when you get successful and have tons of users pouring on your site. See, a no-brainer!

Source de l’article sur DZONE

Gradle Kotlin DSL 1.0 release candidate is generally available, including Gradle 4.10. The Kotlin DSL is nearly ready for widespread use.

We want you to enjoy a build authoring experience with the benefits provided by Kotlin’s static type system: context-aware refactoring, smart content assist, debuggable build scripts, and quick access to documentation. In case you haven’t seen it, you can watch Rodrigo B. de Oliveira demonstrate these benefits in this KotlinConf 2017 video.

Source de l’article sur DZONE

Up to this point, our users can send and receive messages, but we don’t have a way to show them all of their conversations, only one conversation at a time and they have to guess who messaged them before they can see those, which is not very useful. What we need is a directory of all the conversations our user is part of. Let’s go ahead and add this feature to tie things together.

In our Conversations class, we will add a new method "getConversations":

Source de l’article sur DZONE

For the last seven years of my career, I have been living the Agile methodology.  Needless to say, participating in the periodic ceremonies have become commonplace for me.  

Following the example I created when my 100th article on DZone was published on April 5, 2017, my 200th article for DZone will be a retrospective of my last 99 articles – spanning from April 13, 2017 through August 24, 2017.  I plan to cover what fared well with DZone readers and what failed to connect to the same audience. 

Source de l’article sur DZone (Agile)