I see a class of data are not well covered by existing standards. I call them "Infrastructure Secrets". Infrastructure Secrets are credentials or secrets that are commonly used to build or deploy applications and that they are often shared with third party services.
Dr. Sallyann Freudenberg talked about neuro-diversity in the work place at QCon London. Programming is a complex creative task, and Freudenberg explored a number of the techniques that programmers in general use to help them achieve it.
Right now, we in technology are witnessing the convergence of two competing forces: on one hand, an increasing need for security (as demonstrated by these events last year); on the other, an increasing number of organizations adopting Continuous Integration (CI). In a CI model, code is integrated regularly — usually several times a day — and checked against automated tests. Coupled with Continuous Delivery and Continuous Deployment, CI is getting code into live applications faster. While Continuous Integration is improving the agility and speed-to-market of software organizations, that speed can leave developers more vulnerable to security breaches.
Rate this post You’ve probably seen a long, recursive discussion on twitter about #NoEstimates. Some of you, like William Gill may be even interested in a more concrete description that you can apply in your own projects. So here it is. This is my first attempt at a #NoEstimates How To, first presented at Turku …
Centralized development is better than distributed. Test-driven development is better than conventional. Organizational structure can predict code quality. Hallmarks of conventional software-engineering wisdom have never been tested empirically—until now.
We've all seen them: Ambitious projects, starting out with grand visions, ending up as costly lessons in what not to do, leaving behind the ruins of promising paradigms, technologies, tools, and careers. But why do architecture approaches sometimes hurt instead of providing value? Why has "architect" become a negative term for some people? And what can we do to improve our own work? In this keynote, we'll look at some of the most common pitfalls that ensure you'll come up with a disaster, and discuss how they can be avoided.
It seems this week more SAFe related stuff than usual made it across my desk… some positive, some negative… some old, some new… but all asking the same fundamental questions. Is SAFe the savior of all things software development? Is SAFe really agile or merely the second coming of RUP? Will SAFe survive or be …
Computer security, or the lack thereof, has made many headlines recently. In this article we'll look at how bad things are and what you, as a software developer, can do about it. It will help get you started or hopefully give you some new ideas if you're already doing some security work.
At QCon London 2015, Dave Farley proposed that although the state of software development has been suboptimal in the past, studies are revealing that the implementation of continuous delivery leads to considerable improvement. Farley stated that continuous delivery changes the economies of software development, and provides more rapid business idea validation and reduced defect rates.
Sharing your scoops to your social media accounts is a must to distribute your curated content. Not only will it drive traffic and leads through your content, but it will help show your expertise with your followers.
How to integrate my topics' content to my website?
Integrating your curated content to your website or blog will allow you to increase your website visitors’ engagement, boost SEO and acquire new visitors. By redirecting your social media traffic to your website, Scoop.it will also help you generate more qualified traffic and leads from your curation work.
Distributing your curated content through a newsletter is a great way to nurture and engage your email subscribers will developing your traffic and visibility.
Creating engaging newsletters with your curated content is really easy.