Agile/Scrum Training Classes in Lafayette, Indiana
Learn Agile/Scrum in Lafayette, Indiana and surrounding areas via our hands-on, expert led courses. All of our classes either are offered on an onsite, online or public instructor led basis. Here is a list of our current Agile/Scrum related training offerings in Lafayette, Indiana: Agile/Scrum Training
Agile/Scrum Training Catalog
Course Directory [training on all levels]
- .NET Classes
- Agile/Scrum Classes
- Ajax Classes
- Android and iPhone Programming Classes
- Blaze Advisor Classes
- C Programming Classes
- C# Programming Classes
- C++ Programming Classes
- Cisco Classes
- Cloud Classes
- CompTIA Classes
- Crystal Reports Classes
- Design Patterns Classes
- DevOps Classes
- Foundations of Web Design & Web Authoring Classes
- Git, Jira, Wicket, Gradle, Tableau Classes
- IBM Classes
- Java Programming Classes
- JBoss Administration Classes
- JUnit, TDD, CPTC, Web Penetration Classes
- Linux Unix Classes
- Machine Learning Classes
- Microsoft Classes
- Microsoft Development Classes
- Microsoft SQL Server Classes
- Microsoft Team Foundation Server Classes
- Microsoft Windows Server Classes
- Oracle, MySQL, Cassandra, Hadoop Database Classes
- Perl Programming Classes
- Python Programming Classes
- Ruby Programming Classes
- Security Classes
- SharePoint Classes
- SOA Classes
- Tcl, Awk, Bash, Shell Classes
- UML Classes
- VMWare Classes
- Web Development Classes
- Web Services Classes
- Weblogic Administration Classes
- XML Classes
- DOCKER WITH KUBERNETES ADMINISTRATION
8 July, 2024 - 12 July, 2024 - RHCSA EXAM PREP
17 June, 2024 - 21 June, 2024 - Linux Fundaments GL120
15 July, 2024 - 19 July, 2024 - Introduction to C++ for Absolute Beginners
20 May, 2024 - 21 May, 2024 - Ruby on Rails
22 August, 2024 - 23 August, 2024 - See our complete public course listing
Blog Entries publications that: entertain, make you think, offer insight
The Zen of Python, by Tim Peters has been adopted by many as a model summary manual of python's philosophy. Though these statements should be considered more as guideline and not mandatory rules, developers worldwide find the poem to be on a solid guiding ground.
Beautiful is better than ugly.
Explicit is better than implicit.
Simple is better than complex.
Complex is better than complicated.
Flat is better than nested.
Sparse is better than dense.
Readability counts.
Special cases aren't special enough to break the rules.
Although practicality beats purity.
Errors should never pass silently.
Unless explicitly silenced.
In the face of ambiguity, refuse the temptation to guess.
There should be one-- and preferably only one --obvious way to do it.
Although that way may not be obvious at first unless you're Dutch.
Now is better than never.
Although never is often better than *right* now.
If the implementation is hard to explain, it's a bad idea.
If the implementation is easy to explain, it may be a good idea.
Namespaces are one honking great idea -- let's do more of those!
Millions of people experienced the frustration and failures of the Obamacare website when it first launched. Because the code for the back end is not open source, the exact technicalities of the initial failings are tricky to determine. Many curious programmers and web designers have had time to examine the open source coding on the front end, however, leading to reasonable conclusions about the nature of the overall difficulties.
Lack of End to End Collaboration
The website was developed with multiple contractors for the front-end and back-end functions. The site also needed to be integrated with insurance companies, IRS servers, Homeland Security servers, and the Department of Veterans Affairs, all of whom had their own legacy systems. The large number of parties involved and the complex nature of the various components naturally complicated the testing and integration of each portion of the project.
The errors displayed, and occasionally the lack thereof, indicated an absence of coordination between the parties developing the separate components. A failed sign up attempt, for instance, often resulted in a page that displayed the header but had no content or failure message. A look at end user requests revealed that the database was unavailable. Clearly, the coding for the front end did not include errors for failures on the back end.
Bloat and the Abundance of Minor Issues
Obviously, numerous bugs were also an issue. The system required users to create passwords that included numbers, for example, but failed to disclose that on the form and in subsequent failure messages, leaving users baffled. In another issue, one of the pages intended to ask users to please wait or call instead, but the message and the phone information were accidentally commented out in the code.
While the front-end design has been cleared of blame for the most serious failures, bloat in the code did contribute to the early difficulties users experienced. The site design was heavy with Javascript and CSS files, and it was peppered with small coding errors that became particularly troublesome when users faced bottlenecks in traffic. Frequent typos throughout the code proved to be an additional embarrassment and were another indication of a troubled development process.
NoSQL Database
The NoSQL database is intended to allow for scalability and flexibility in the architecture of projects that will use it. This made NoSQL a logical choice for the health insurance exchange website. The newness of the technology, however, means personnel with expertise can be elusive. Database-related missteps were more likely the result of a lack of experienced administrators than with the technology itself. The choice of the NoSQL database was thus another complication in the development, but did not itself cause the failures.
Another factor of consequence is that the website was built with both agile and waterfall methodology elements. With agile methods for the front end and the waterfall methodology for the back end, streamlining was naturally going to suffer further difficulties. The disparate contractors, varied methods of software development, and an unrealistically short project time line all contributed to the coding failures of the website.
I’ve been a technical recruiter for several years, let’s just say a long time. I’ll never forget how my first deal went bad and the lesson I learned from that experience. I was new to recruiting but had been a very good sales person in my previous position. I was about to place my first contractor on an assignment. I thought everything was fine. I nurtured and guided my candidate through the interview process with constant communication throughout. The candidate was very responsive throughout the process. From my initial contact with him, to the phone interview all went well and now he was completing his onsite interview with the hiring manager.
Shortly thereafter, I received the call from the hiring manager that my candidate was the chosen one for the contract position, I was thrilled. All my hard work had paid off. I was going to be a success at this new game! The entire office was thrilled for me, including my co-workers and my bosses. I made a good win-win deal. It was good pay for my candidate and a good margin for my recruiting firm. Everyone was happy.
I left a voicemail message for my candidate so I could deliver the good news. He had agreed to call me immediately after the interview so I could get his assessment of how well it went. Although, I heard from the hiring manager, there was no word from him. While waiting for his call back, I received a call from a Mercedes dealership to verify his employment for a car he was trying to lease. Technically he wasn’t working for us as he had not signed the contract yet…. nor, had he discussed this topic with me. I told the Mercedes office that I would get back to them. Still not having heard back from the candidate, I left him another message and mentioned the call I just received. Eventually he called back. He wanted more money.
I told him that would be impossible as he and I had previously agreed on his hourly rate and it was fine with him. I asked him what had changed since that agreement. He said he made had made much more money in doing the same thing when he lived in California. I reminded him this is a less costly marketplace than where he was living in California. I told him if he signed the deal I would be able to call the car dealership back and confirm that he was employed with us. He agreed to sign the deal.
Tech Life in Indiana
training details locations, tags and why hsg
The Hartmann Software Group understands these issues and addresses them and others during any training engagement. Although no IT educational institution can guarantee career or application development success, HSG can get you closer to your goals at a far faster rate than self paced learning and, arguably, than the competition. Here are the reasons why we are so successful at teaching:
- Learn from the experts.
- We have provided software development and other IT related training to many major corporations in Indiana since 2002.
- Our educators have years of consulting and training experience; moreover, we require each trainer to have cross-discipline expertise i.e. be Java and .NET experts so that you get a broad understanding of how industry wide experts work and think.
- Discover tips and tricks about Agile/Scrum programming
- Get your questions answered by easy to follow, organized Agile/Scrum experts
- Get up to speed with vital Agile/Scrum programming tools
- Save on travel expenses by learning right from your desk or home office. Enroll in an online instructor led class. Nearly all of our classes are offered in this way.
- Prepare to hit the ground running for a new job or a new position
- See the big picture and have the instructor fill in the gaps
- We teach with sophisticated learning tools and provide excellent supporting course material
- Books and course material are provided in advance
- Get a book of your choice from the HSG Store as a gift from us when you register for a class
- Gain a lot of practical skills in a short amount of time
- We teach what we know…software
- We care…