Last week I participated as a panelist in the Continuous Discussions talk hosted by Electric Cloud, and the recording is now available. A bit long but there are some good points in there.
Back in the old days when the need for localized string arose, I would add a new string and use AppResources to access the correct string in code. In the new universal apps the story is a bit different.
Submodules are one of the most powerful and most mistrusted features in git, at least in the web development part of the internet where I spend my time. I've seen them go horribly wrong, but I've also had teams adopt submodules and have their development process run much more smoothly as a result.
From software developer Curtis Lassam (who writes about comics and code) comes a comic series called Cube Drone. This is Cube Drone #3: Purple Hazing.
Yesterday's announcement states that PSU releases (which are really CPU+ releases) will be released along with their corresponding CPU releases.
Over the last years Continuous Delivery has gained a massive following with many development teams embracing the style. Companies have chosen (as with many other modern developer tools), to either build their own or embrace a hosted service.
We are not the first industry to face this challenge. But many are convinced our problem is much smaller than it really is or that it does not exist. They simply ignore it. Or choose to do nothing about it. Meanwhile, the problem is multiplying like rabbits.
How can we try to figure out where the weak points are in our security? How can we find the tasks to work on to beef up security? One option is to perform a threat analysis.
First and foremost, you now have access to the history of your JVMs.
Once, people used the word genius only when describing someone who really was a genius. Today every parent uses this word to describe their, likely cognitively regular child. I find the same trend holds true for DevOps. And yet, that doesn't stop everyone from saying the word DevOps, a lot (and more often than not, in a completely wrong context).
DevOps requires new practices and smart players. Panelists at the #C9D9 hangout shared their real world DevOps stories, and want to spark a continuous discussion.
This article represents different aspects of process discovery phase which is key to any business process implementation project. The analogy to process discovery phase in regular software project is “requirements gathering phase”.
As co-founder of Logentries I am often asked – “Why Logs?” And I have to admit, upon first impression, ‘log management and analytics’ does not seem like the sexiest space.
You want to check an API to ensure that it’s secure, but just how do you think like a bad guy intent on breaking your API and potentially into your site? Performing the right sorts of API security testing is essential.
With the first release of JavaFX 2, Oracle introduced the javafxpackager tool, which has now been renamed to javapackager (Java 8 u20). This enables developers to create native executables for any common platform, even mac app store packages.
Troubleshooting an app based on one error is hard. How do you add context to the exception?
This issue comes when your application uses a bigger key size in encryption than the default key size provided by the Java runtime.
Out of the box, Go provides just enough package management to make for a fast and efficient compiler. While it's not opinionated enough to drive anyone away, Go package management doesn't have the features to meet the needs of many developers.
Our modern workplaces are often a hive of activity, whether it’s the hubbub of conversation across our open plan offices or the multitude of digital disruptions busting to interrupt our flow of thought.
It may mean the difference between a 15 minute meeting where everyone nods their heads, and a day long battle of egos.
Continuous integration is the practice of merging all developers’ working copies with a shared mainline and making a build several times a day. CI is used to prevent integration problems, to improve software quality, and to reduce the time taken to deliver. Continuous Integration is derived from the early practice of XP (Extreme Programming) where a team integrates the code change more often to avoid descending into 'integration hell'.
We’re working hard in the Logentries towers to integrate our continuous delivery tools, so we can identify and track issues as easily as possible. This saves us time that we can spend on important things like adding new features (or playing pool!).
I was introduced to Niko-niko calendars by Max Webster at Niko Niko. Basically, they are a way of tracking a team’s mood over time. At the end of the day, team members put in a smile/frown/whatever face indicating their mood.
I highly recommend this to anyone who wants to learn more about securing their network setup, know your enemy and you'll be a head of the crowd.
A Continuous Delivery pipeline is an automated representation of the value stream of an organisation, and rules are often codified in a pipeline to reflect the real-world journey of a product increment.