CloudBees employees travel the world to a lot of interesting events. This month the Bees are busy. If you are attending any of these November events, be sure to connect with us!
- W-JAX'14 Business Technology Days, München - 4th until 6th of November
As the leading conference for enterprise technologies, agile methods and software architectures, the W-JAX offers a program that is unique in its theme and experts density. In more than 180 sessions, workshops and keynotes the W-JAX deals with a wide range of current and future-oriented technologies such as Java and Scala, Agile development models as well as modern and efficient enterprise architectures.Together with the accompanying Business Technology Days this event gives IT professionals from companies in all industries the decisive impulses for digital value creation and innovation. You can visit the website for more information and to register.
- Continuous Lifecycle 2014 Conference Mannheim – 10th of November The continuous Lifecycle Conference is dedicated to integrated concepts, processes and tools of Continuous Delivery, DevOps and Agile ALM. Attendees will for instance learn about how to use Continuous Delivery correctly, testing, change management and about the practical implementation of DevOps methods. The Conference is intended for software developers, software architects, administrators, project leaders and IT strategists. Last year’s edition of the continuous Lifecycle Conference was quickly sold out, so this year it will be held in the bigger congress center Rosengarten in Mannheim. There will be high profile keynote speakers, full day workshops, a panel with proven experts and much more. If you want to be kept informed about the further progress of the conference click here. To register click here and for more information click here.
- AWS Re:invent Las Vegas – 11th until 14th of November Join the largest gathering of the global Amazon Web Services community at AWS re:Invent 2014. Whether you are an existing customer or new to the cloud, you will leave AWS re:Invent with the knowledge and skills to refine your cloud strategy, improve developer productivity, increase application performance and security, and reduce infrastructure costs. You will gain deeper knowledge of AWS services and learn best practices with unique insights from real customers. Choose from 200+ technical sessions covering architecture, operations, security, and more. There will also be technical boot camps, self-paced labs and hackathons. For more information, to watch the after movie from the re:Invent 2013 and to register you can visit the website.
- Breakfast briefing: “Making DevOps Happen” - 12th of November
Join us at this breakfast briefing at The Royal Exchange in London to hear from Stephen Thair (DevOpsGuys), Helen Beal (Ranger4) and Wayne Collier (CloudBees) about how to get started with DevOps and how to give yourself the best chance of success. Learn how DevOps takes innovation to market faster, drives Continuous Delivery and how it delivers real, measurable results. To register and to have a look at the agenda visit the event page.
- CD Summit Washington D.C. – 19th of November The last CD Summit of this year will be in Washington D.C., so IT executives and technologists who could not attend to the other CD Summits make sure you’re there. Come join an impressive group of continuous delivery experts to explore how you can increase quality and much more. You will learn how to make evolutionary changes to people, processes and technologies to achieve the benefits of continuous delivery and agile. . There will be eight speakers, four in the executive morning and four in the technical afternoon, from various technical related companies and of course from CloudBees. For more information and to register just click here.
- CI and CD Across the Enterprise with Jenkins Webinar - 19th of November
Delivering value to the business faster thanks to Continuous Delivery and DevOps is the new mantra of IT organizations. In this webinar, CloudBees will discuss how Jenkins, the most popular open source Continuous Integration tool, allows DevOps teams to implement Continuous Delivery. You will learn how to orchestrate Continuous Delivery pipelines with the new workflow feature, scale Jenkins horizontally in your organization using Jenkins Operations Center by CloudBees and how to implement end to end traceability with Jenkins and Puppet and Chef. Click here for more information and there is a limited registration, so don't wait!
Get firsthand training with Ranorex professionals and learn how to get the most out of Ranorex Studio at one of these workshops.
Look at the schedules for additional workshops in the next few months.
After analyzing the results of our 2014 State of Medical Device Development survey, we identified some interesting traceability trends, which are summarized in this infographic:
To see the full results, download the State of Medical Device Development 2014 report free.Share on Technorati . del.icio.us . Digg . Reddit . Slashdot . Facebook . StumbleUpon
To read more, visit our blog at blog.sonatype.com.
Exploratory testing (ET) is a hot topic within the testing world. Testers who are not familiar with exploratory testing are looking for resources to understand what it is and how to get started testing in this way.
We recently debuted a new course in uTest University called “What is Exploratory Testing?” penned by Lucas Dargis and Allyson Burk. In it, we look at the “traditional” approach to testing, and review what ET is and how it differs from scripted testing.
We also look at why you should use exploratory testing and wrap up by showing testers how to get started. In the course excerpt below, we answer the question: what is exploratory testing?
ET is simultaneous learning, test design and test execution. In other words, the tester is designing his or her tests and executing them at the same time. As an exploratory tester, your next action (the next test) is influenced by your previous actions, your observations of the product’s behavior, and your own thought process.
ET also assumes that a significant portion of the testing will be spent learning about the product. As you explore, you become more aware of how the product functions and its expected behavior. You can use that knowledge to design new and better tests. It also helps improve the analysis of the test’s results.
It is important to make the distinction between ET and other types of unscripted testing because some testers mistakenly believe that all unscripted testing is simply poking the product randomly to see what happens. Performing a series of random actions is called monkey testing and in some cases it may be a valid approach, however this is quite different from ET. With ET actions are the opposite of random — they are deliberate, driven by human thought and reasoning. Your approach is continually refined as new information is gathered and analyzed.
When an explorer goes to an uncharted region of the world, they spend months preparing. They go with a goal in mind and they rely on their abilities to adapt to changing situations. Similarly, an exploratory tester must prepare. They too have a goal and the skills needed to adjust their course. It’s true that monkey testing may occasionally find useful information, but it’s found unexpectedly. It’s the difference between discovery and exploration; luck versus skill.
Want to read more about exploratory testing? Read the full uTest University course!Live Exploratory Testing Webinar
Learn about the basics of exploratory testing, what it means to exploratory test, and then watch Lucas as he embarks on an exploratory testing session. There will be a Q&A session at the end, so don’t miss this unique live testing event! Register for this webinar, happening on November 5, 2014, from 2:00 PM to 3:00 PM Eastern Time. After registering, you will receive a confirmation email containing information about the webinar.
uTest University is free for all members of the uTest Community. We are constantly adding to our course catalog to keep you educated on the latest topics and trends. If you are an expert in UX, load & performance, security, or mobile testing, you can share your expertise with the community by authoring a University course. Submit your course ideas today.
At the recent DevOps Enterprise Summit, Nicole Forsgren an Assistant Professor at Utah State delivered a compelling presentation on the business impact of DevOps (embedded below). Nicole pointed out that historically, investment in IT has not delivered sustainable business advantage. If I can get an advantage by buying a server, my competitor can match that quickly.
What’s emerging from studies on DevOps is different though. Publicly traded companies that are doing well with DevOps are drastically out-performing in business terms, and market cap. A shift to DevOps in IT appears to be mirroring a shift to Lean in manufacturing. Very cool.
The key take-away is that while DevOps is supported by investments in IT. The big shift is a new business processes. New ways of working. It’s culture supported by tools that wins the day, not just buying another server.
Michael Moshe is a Gold-rated tester and Test Team Lead (TTL) at uTest hailing from Calgary, Alberta, Canada. He joined the community just over three years ago. You can reach Michael on LinkedIn, @xtalentbiz on Twitter, his IT employment website, and learn more about the book he recently authored on finding the right job in IT.
Be sure to also follow Michael’s profile on uTest as well so you can stay up to date with his activity in the community!
uTest: Android or iOS?
Michael: I use both — each has its strengths and weaknesses. When you get used to either, it doesn’t matter where to look for bugs.
uTest: What drew you into testing initially? What’s kept you at it?
Michael: It was the second year of my computer science studies at some boring lecture. The secretary enters the class and posts a QA opening note on the job board. The teacher says, “See, this is what will happen to you if you fail as a developer.” I applied and got that job! 8 years later, I believe that this was the best decision I’ve ever made, along with joining uTest.
On every single interview, I’ve been asked, “Why QA?” I was always saying that I just love it and I’m good at it, but the truth is that QA is a great way to make good money (while having fun) without a specific set of skills — it is the mindset that matters. For example, at uTest, all you need is motivation, dedication, communication skills, the willingness to learn and improve, patience and a bit of luck to become a TTL, Community Project Manager (CPM), Project Manager (PM), or even work onsite as QA for a big customer.
uTest: What’s your go-to gadget?
Michael: Samsung Galaxy Note 3 — an amazing toy and big enough to work with uTest chat.
uTest: What’s one trait or quality you seek in a fellow software testing colleague?
Michael: That we’re on the same boat. I would expect that my fellow testers, TTLs, PMs, Community Managers (CMs) and the customer be responsive and help each other.
uTest: What was the greatest challenge you’ve had to overcome on your testing team? How did you get through it?
Michael: My greatest challenge happened a short time ago at uTest as a TTL Premier with a very small testing team that was handpicked. The challenge was that we had a very small team who the knew product, and the customer asked us to run at least one 24-hour cycle every day for over a month. Sometimes it was 2 or 3 cycles a day, not to mention, all the Bug Fix Verification (BFV) cycles for all the bugs that were found every cycle. Also, the customer had a lot of specific requests to try and reproduce multiple bugs again and again on the test environments after refresh. We overcame this challenge together, and everyone did their best to keep everyone happy.
uTest: What keeps you busy outside testing?
Michael: During my professional experience and without planning, I became pretty good at job hunting. At some point, I decided to start a business and help others to find the perfect job. After writing a few books and creating a website, I realized that this is more of a hobby for me than a business, and I went back to full-time QA and uTest. My books and website are still alive, and I try to maintain them. Maybe you’ll find them useful in your next job hunt.
There are many names for leadership roles in software development such as Senior Developer, Architect, Technical Lead, Team Lead, and Engineering Manager. These are just a few. To me, the Technical Leader (Tech Lead) plays an unique and essential role that others cannot.The Definition
The Short: A Tech Lead is a developer who is responsible for leading a development team.
The Long: Leading a development team is no easy task. An effective Tech Lead establishes a technical vision with the development team and works with developers to turn it into reality. Along the way, a Tech Lead takes on traits that other roles may have, such as a Team Lead, Architect or Software Engineering Manager but they remain hands-on with code.
To make the most effective choices and to maintain trust and empathy with developers, a Tech Lead must code. In “The Geek’s Guide to Leading Teams” presentation, I talked about an ideal minimum time of about 30%.
Not just a Team Lead
An extract from the The Geek’s Guide to Leading Teams presentation
Early in my career, I worked on a team that had both a Tech Lead and a Team Lead. The Team Lead didn’t have much of a technical background and had a strong focus on the people side and tracking of tasks. They would have 1-to-1s with people on the team, and co-ordinate with outside stakeholders to schedule meetings that didn’t interrupt development time where possible.
While the Team Lead focused on general team issues, the Tech Lead focused on technical matters that affected more than just one developer. They stepped in on heated technical debates, and worked with outside stakeholders to define technical options and agree on solutions for future streams of work. They wrote code with the other developers and sometimes called for development “huddles” to agree on a direction.More hands-on than an Engineering Manager
You manage things, you lead people – Grace Hopper
Any reasonably-sized IT organisation has an Engineering Manager. They are responsible for more than one development, and have tasks that include:
- Maintaining a productive working environment for development teams.
- Acquiring appropriate budget for development to support business goals.
- Representing the technology perspective on a management or board level.
- Establishes and/or co-ordinates programmes of work (delivered through development).
- Responsible for overall IT headcount.
Depending on the size of an organisation, an Engineering Manager may also be called a Chief Technical Officer (CTO) or Chief Information Officer (CIO) or Head of Software Development.
Although an Engineering Manager represents technology, they are often very far-removed from a development team and rarely code. In contrast, a Tech Lead sits with developers, very much focused on moving them towards their goal. They work to resolve technical disputes, and are watchful of technical decisions that have long-term consequences. A Tech Lead works closely with the Engineering Manager to build an ideal work environment.A good Architect looks like a Tech Lead
The Architect role ensures overall application architecture suitably fits the business problem, for now and for the future. In some organisations, Architects work with the team to establish and validate their understanding of architecture. A suitable amount of standardisation helps productivity. Too much standardisation kills innovation.
Some organisations have the “Ivory Tower Architect” who swoops in to consult, standardise and document. They float from team-to-team, start new software projects, and rarely follow up to see the result of their initial architectural vision.
An effective Architect looks like a good Tech Lead. They establish a common understanding of what the team is aiming for, and make adjustments as the team learns more about the problem and the technology chosen to solve it.What is a Tech lead again?
A successful Tech Lead takes on responsibilities that sit with roles such as the Team Lead, the Architect and the Engineering Manager. They bring a unique blend of leadership and management skills applied in a technical context with a team of developers. The Tech Lead steers a team towards a common technical vision, writing code at least 30% of the time.
If you liked this article exploring the Tech Lead role, you will be interested in “Talking with Tech Leads,” a book that shares real life experiences from over 35 Tech Leads around the world. Now available on Leanpub.
Every once in a while I read something like this:
Yeah, [TDD|BDD|ATDD] is great. But how do you convince [your manager|your employer|your colleagues] to get the time to do it?
In the past week I decided that I need something to point folks to when this questions comes up again. So, here it is.
First of all, I think it helps to apply a lesson that I learned years ago as a swimming trainer. I had several exercises in my repertoire that were a bit unusual, and at times hard to do. These included variations of swimming strokes in unusual positions.
Every now and then when I gave out one of the exercises to the kids, some or all of them were complaining: “this doesn’t work”, “I can’t swim like that”, etc.
What the kids didn’t know was that I had learned to try out these exercises on my own first to get a grasp of how difficult they were. Thereby I also knew that they were possible to do. Over time, I realized that “this doesn’t work” could be easily translated to “I don’t know how I can make this work”, and tada, let me see how I can help you with that.
Today, I apply the same lesson to TDD. Whenever someone tells me that TDD does not work in his code base, well, I make the mental translation to “I don’t know how TDD works on my code base”, and off we go.My boss won’t let me
Yeah, right. Here’s a hard message for you: are you telling your carpenter how to hold his hammer? Are you telling your plumber how to use the pipe wrench? Are you telling your car mechanic when to replace the oil filter?
Seriously, why is your boss, your project manager or whatever excuse you have not use TDD telling you how to do your job? I thought you are a highly educated knowledge worker. If you are convinced about the effectiveness of TDD, then no boss or project manager should be telling you how to do your job.
Oh, sorry, there actually is one case when this might be appropriate for your boss to tell you. When you are not able to deliver working software that adheres to the business goals using TDD.
But remember: that’s feedback about how you use TDD, not about how bad your boss or project manager may be. So, better practice applying TDD and helpful design practices to be able to better serve the projects you are working on.TDD does not work with my [language|framework|etc.]
Sure. That’s an easy excuse. Yeah, those darn language or framework programmers weren’t helpful. That’s how it’s going to work.
Uhm, wait a minute. What do you think how old TDD actually is? A thing from the Smalltalk community? It turns out, not quite right.
A while ago, Arialdo Martini wrote a blog entry on how old TDD actually is. Click that link, go there. Make sure, to read it up until the end. I’ll wait here with my rant.
Surprised? So was I – to some extent. Besides the fact that things like TDD have been mentioned in papers and publication by Dijkstra, and the first NATO conferences, TDD actually is way older than that.
Also note what Jerry Weinberg says in this interview with Michael Bolton about TDD:
Michael: [...] I’ve learned about both from conversations that I’ve had with you and other smart people. I remember once that Joshua Kerievsky asked you about why and how you tested in the old days—and I remember you telling Josh that you were compelled to test because the equipment was so unreliable. Computers don’t break down as they used to, so what’s the motivation for unit testing and test-first programming today?
Jerry: We didn’t call those things by those names back then, but if you look at my first book (Computer Programming Fundamentals, Leeds & Weinberg, first edition 1961 —MB) and many others since, you’ll see that was always the way we thought was the only logical way to do things. I learned it from Bernie Dimsdale, who learned it from von Neumann.
When I started in computing, I had nobody to teach me programming, so I read the manuals and taught myself. I thought I was pretty good, then I ran into Bernie (in 1957), who showed me how the really smart people did things. My ego was a bit shocked at first, but then I figured out that if von Neumann did things this way, I should.
John von Neumann was a lot smarter than I’ll ever be, or than most people will ever be, but all that means is that we should learn from him.[...]
So, the next time your boss approaches you asking to leave out those unit tests or stop that TDD thing, tell them the story on how Jerry Weinberg learned it from Bernie Dimsdale who learned it from John von Neumann. Then ask them that you don’t consider yourself smarter than John von Neumann.
Oh, and besides, even though some of our hardware became more reliable, most of our software hasn’t. When answering the question why we ever gave up something that John von Neumann taught us, I wouldn’t accept that excuse either.What if all of that doesn’t work?
A couple of years back, I attended a Code Retreat session in Bielefeld. We worked all day using TDD, in six consecutive sessions, always deleting our code at the end, since we strived to learn about TDD, not to come up with a beautiful solution to a long solved problem.
At the end of the day, we held a quick retrospective. Everyone shared what they learned that day, and what they would be doing differently back at work next Monday. One guy stepped forward and said that he would change jobs on Monday since he never would be able to use TDD at his current job. Now, after he experienced it, he never wanted to do anything else.
That said, of course the “change your organization or change your organization” phrase also applies to TDD. If you are convinced about the approach, and never want to do anything else, and your environment currently doesn’t support it, well, move ahead.
In case you want to learn more, attend one of the events for the Global Day of Code Retreat in two weeks. Since I always learn one little thing at each of these events, I will be attending the one in Bielefeld, Germany.
There’s always one day out of the year the uTest Community Management team can count on to dress up and look pretty ridiculous. Leave it to Halloween.
Yesterday, as part of each department of Applause’s goal of an individual costume theme, the uTest Community Management team went ‘Under the Sea.’ Enjoy some of the hilarity — and general unsettling nature of — yesterday’s office Halloween antics.
Happy Halloween.Click to view slideshow.
There’s growing research that suggests that sitting down all day is bad for you so in a bid to live longer and see my sons growing up I’ve started using a standup desk at work. A few others here at NewVoiceMedia are also using standing desks. I also thought I’d have a go at building a standing … Read More →
We have been covering code for over a decade. During that time, we have learned a lot from our customers on how to make the most out of implementing meaningful code coverage to teams. We thought it may help if we put together some of the highlights we have learned about the best practices of .NET code coverage and share them with you.
This webinar outlines four categories of best practices, with examples, to guide development efforts and improve overall code quality. The first category focuses on code coverage metrics and the three we rely on in our own organization. The second category outlines how code coverage best practices can be employed as a team. The third category reviews techniques for effectively capturing code coverage data. The fourth, and final category, relates specifically to NCover and how to keep your system optimized.This webinar outlines four categories of best practices, with examples, to guide development efforts and improve overall code quality. Previously recorded and available for immediate viewing.
It’s 4 days until the Melbourne Cup, a horse race that literally stops a nation. It’s the single biggest betting event in the sporting year, and a huge percentage of the population will have a little wager. What’s the easiest way to place that bet? Online… So I thought I’d run some tests on the […]
The post Form guide – which betting agency website will win the Melbourne Cup? appeared first on Dynatrace APM Blog.