Leipzig , Germany CompTIA Training

Since you asked for the three most important things that non-programmers should know about, and I’ve spent most of my career working with more non-programmers than programmers, I have a few interesting things that would help.

Number One - It Is Impossible To Accurately Estimate Software Projects

No matter what is tried. No matter what tool, agile approach, or magic fairy dust people try to apply to creating software… accurately predicting software project timelines is basically impossible.

There are many good reasons for this. Usually, requirements and feature ideas change on a daily/weekly basis. Often it is impossible to know what needs to be done without actually digging into the code itself. Debugging and QA can take an extraordinary amount of time.

And worst of all…

Project Managers are always pushing for shorter timelines. They largely have no respect for reality. So, at some point they are given estimates just to make them feel better about planning.

No matter how much planning and estimation you do, it will be wrong. At best it will be directionally correct +/- 300% of what you estimated. So, a one year project could actually take anywhere between 0 and 5 years, maybe even 10 years.

If you think I’m joking, look at how many major ERP projects that go over time and over budget by many years and many hundreds of millions of dollars. Look at the F-35 fighter jet software issues.

Or in the small, you can find many cases where a “simple bug fix” can take days when you thought it was hours.

All estimates are lies made up to make everyone feel better. I’ve never met a developer or manager who could accurately estimate software projects even as well as the local weatherman(or woman) predicts the weather.

Number Two - Productivity Is Unevenly Distributed

What if I told you that in the average eight hour work day the majority of the work will get done in a 30 minute timeframe? Sound crazy?

Well, for most programmers there is a 30–90 minute window where you are extraordinarily productive. We call this the flow state.

Being in the flow state is wonderful and amazing. It often is where the “magic” of building software happens.

Getting into flow can be difficult. It’s akin to meditation in that you have to have a period of uninterrupted focus of say 30 minutes to “get in” the flow, but a tiny interruption can pull you right out.

Now consider the modern workplace environment. Programmers work in open office environments where they are invited to distract each other constantly.

Most people need a 1–2 hour uninterrupted block to get 30–90 minutes of flow.

Take the 8 hour day and break it in half with a lunch break, and then pile in a few meetings and all of a sudden you are lucky to get one decent flow state session in place.

That is why I say that most of the work that gets done happens in a 30 minute timeframe. The other 7–8 hours are spent being distracted, answering email, going to meetings, hanging around the water cooler, going to the bathroom, and trying to remember what you were working on before all these distractions.

Ironically, writers, musicians, and other creative professionals have their own version of this problem and largely work alone and away from other people when they are creating new things.

Someday the programming world might catch on, but I doubt it.

Even if this became obvious, it doesn’t sit well with most companies to think that programmers would be paid for an 8 hour day and only be cranking out code for a few hours on a good day. Some corporate middle manager would probably get the bright idea to have mandatory flow state training where a guru came in and then there would be a corporate policy from a pointy haired boss mandating that programmers are now required to spend 8 hours a day in flow state and they must fill out forms to track their time and notify their superiors of their flow state activities, otherwise there would be more meetings about the current flow state reports not being filed correctly and that programmers were spending too much time “zoning out” instead of being in flow.

Thus, programmers would spent 7–8 hours a day pretending to be in flow state, reporting on their progress, and getting all their work done in 30 minutes of accidental flow state somewhere in the middle of all that flow state reporting.

If you think I’m joking about this, I’m not. I promise you this is what would happen to any company of more than 2 employees. (Even the ones run by programmers.)

Number Three - It Will Cost 10x What You Think

Being a programmer, I get a lot of non-programmers telling me about their brilliant app ideas. Usually they want me to build something for free and are so generous as to pay me up to 5% of the profits for doing 100% of the work.

Their ideas are just that good.

Now, I gently tell them that I’m not interested in building anything for free.

At that point they get angry, but a few ask how much it will cost. I give them a reasonable (and very incorrect) estimate of what it would cost to create the incredibly simple version of their app idea.

Let’s say it’s some number like $25,000.

They look at me like I’m a lunatic, and so I explain how much it costs to hire a contract programmer and how long it will actually take. For example’s sake let’s say it is $100/hr for 250 hours.

To be clear, these are made up numbers and bad estimates (See Number One for details…)

In actuality, to build the actual thing they want might cost $250,000, or even $2,500,000 when it’s all said and done.

Building software can be incredibly complex and expensive. What most people can’t wrap their head around is the fact that a company like Google, Apple, or Microsoft has spent BILLIONS of dollars to create something that looks so simple to the end user.

Somehow, the assumption is that something that looks simple is cheap and fast to build.

Building something simple and easy for the end user is time consuming and expensive. Most people just can’t do it.

So, the average person with a brilliant app idea thinks it will cost a few hundred or maybe a few thousand dollars to make and it will be done in a weekend is so off the mark it’s not worth considering their ideas.

And programmers are too eager to play along with these bad ideas (by making bad estimates and under charging for their time) that this notion is perpetuated to the average non-programmer.

So, a good rule of thumb is that software will cost 10 times as much as you think and take 10 times as long to finish.

And that leads to a bonus point…

BONUS - Software Is Never Done

Programmers never complete a software project, they only stop working on it. Software is never done.

I’ve worked at many software companies and I’ve never seen a software project “completed”.

Sure, software gets released and used. But, it is always changing, being updated, bugs get fixed, and there are always new customer requests for features.

Look at your favorite software and you’ll quickly realize how true this is. Facebook, Instagram, Google Search, Google Maps, GMail, iOS, Android, Windows, and now even most video games are never done.

There are small armies of developers just trying to keep all the software you use every day stable and bug free. Add on the fact that there are always feature requests, small changes, and new platforms to deal with, it’s a treadmill.

So, the only way out of the game is to stop working on software. At that point, the software begins to decay until it is no longer secure or supported.

Think about old Windows 3.1 software or maybe old Nintendo Cartridge video games. The current computers and video game consoles don’t even attempt to run that software anymore.

You can’t put an old video game in your new Nintendo Switch and have it “just work”. That is what happens when you think software is done.

When programmers stop working on software the software starts to die. The code itself is probably fine, but all the other software keeps moving forward until your software is no longer compatible with the current technology.

So, those are the four most important things that non-programmers should know about programming. I know you asked for only three, so I hope the bonus was valuable to you as well.

What is Design Thinking and How Does it Apply to HR?

[Jan, 28, 2020] |
Tags:

The Context Of Design Thinking And Its Application In Employee Skill Training

Design thinking is a crucial pillar in today’s problem-solving imperatives. In fact, it is being pursued as a unit course in various institutions across the globe, thus underlying its importance in aiding objective human thinking. It’s not a specific property for designers. Far from it, it has emerged as an innovative solution-seeking tool for all great inventors and innovators.

By description, it is a design methodology used for tackling complex problems that are virtually unknown or ill-defined, through a careful evaluation of the human needs involved, understandably restructuring the problem, by brainstorming to create many solutions, and by adopting a direct approach in testing and prototyping. It helps us come up with creative ways to solve nagging problems that stem from us and especially in the workplace setting.

The ‘overwhelmed/overburdened employee’ is a common term in HR offices across many organizations in the world. Employees are faced with a huge challenge in regards to coping with fast-paced technological and office changes in the working environment. This had led to a massive stagnation in productivity, prompting HR heads to look for new ways to reduce their employees’ stress and workload.

While evaluating many options, this model of thinking has posed as a helpful tool for HR managers when dealing with their vexed employees. IT training, in particular, has helped shape the productive realms of many companies out there.

Let’s explore how this thinking domain can be used to plan employee skill training:

Empathize

If you want to show concern for your employees, first empathize with their situation. Seek to understand the needs of the employees deeply, what they lack, what they need, and the challenges that they are likely facing. This will act as the basis of plotting the problem and working on the next phase of solving it.

You can collect data in this phase through empathy maps and journey maps. In the latter, you endeavor to steadily track the day-to-day activities and tasks of employees. This is achieved through observations or structured interviews. In turn, it aids in elevating the thinking process.

Through empathy maps, you ponder on collected findings and synthesize them keenly. Here, you seek to establish how an employee is thinking, their feelings, and insights into the probable root cause of the problem.

Define the Problem

After a comprehensive analysis of the collected data; the problem definition phase should follow. The idea here is to locate the underlying root of the problem concisely. HR should seek to utilize an analysis framework to help address problems affecting the holistic being of all employees. Therefore, each issue would require a list of underlying causes: lack of motivation, lack of knowledge/understanding, or just lack of skill.

Once the root cause(s) are clearly defined, a clear problem statement should be drawn up alongside performance goals that are firmly based on actual drivers.

Think Solely About Employee-Based Solutions (iterative learning)

Conventionally, customers are at the heart of every organization’s dealings. They inspire and drive the company’s objectives because they are crucial in profit making. However, employees have greatly suffered while working ‘behind the scenes.’ Such situations have led to employees feeling discontent and work under immense pressure, which inevitably leads to underperformance. To avoid this, the experimental learning concept can be utilized by HR offices to engage employees more by creating solutions that directly suit the situations they encounter daily.

Here, trainers are removed as the center of focus. An iterative ‘reflection’ cycle is established to tap continuous employee feedback in a bid to sharpen their skills. This method helps employees adapt to new technology through a well established IT consulting network. In the long run, employees don’t forget how they handled a particular problem, and this effectively raises a firm’s productivity.

Support Employee Tasks with Simple Technology (Ideate)

The simplest way to support employee-working experience is by not sidelining them unprepared with changing technology processes. As an HR Manager, fully engage your employees when transitioning to new tech by making use of effective training or consulting services. Specific training needs can be assessed and addressed within the organization or with a third party industry expert.

According to Deloitte’s 2016 Global Human Capital Trends Report, design thinking was isolated as crucial in crafting the employee experience. 79% of those interviewed identified it as imperative. However, almost a similar percentage agreed that a lot of compliance programs and training are still based on outdated modes of meetings and processes.

The report also recommended the need to put necessary consideration on employees through proper IT training for far colossal efficiency. One way to make this work is by drawing a connected roadmap of skills and information needed at certain work intervals. Shedding off overwhelming and irrelevant amounts of data for new employees is vital in retaining their concentration and output. What’s more, a customizable app can help employees undertake appropriate tasks at the specified time, thus resulting in higher revenue for the long term.

Implementing an Intuitive Tech Learning Approach (Ideate)

The basis of this argument is that not every employee is the same. All of them are differently gifted and shouldn’t be forced to use one inflexible technology or system that doesn’t cater to their individual needs in a buzzing work environment. This mode of critical thinking brings to life personas such that fictive employees representing a defined group of external employees are drawn up. In this set-up, the personas should be able to learn and work efficiently within their own small environment while quickly utilizing their own skill set and the required information to make things work.

An HR manager can replicate this working scenario through the use of role-plays. This can be achieved by conducting short-term soft skills training sessions to sharpen their ability to handle similar situations. In the case of new technology, video-replays on how to use it in a one-on-one customer scenario can help relieve the pressure and spur the employee to be more productive.

Prototype and Testing

Here, the HR Manager should run a couple of tests to ensure whether the desired model of skill training is working. One way to get started is by crafting a simple prototype of the technology required, probably as a single module to establish its viability.

The new technology should be vigorously tested during prototyping to pinpoint any leaks, disjoints, or performance issues. Structured walkthroughs can be implemented to help employees navigate the solution through proper IT training sessions.

What’s more, HR should conduct sessions to get the employees’ views, emotions, or feelings regarding the new solution. In case of any cause for concern, the prototype should be improved until it meets the intermediate needs of its users.

Iterations are also a common occurrence in this phase. Refinements and alterations are curved out to make sure that the final thing suits every employee in some understandable capacity.

Wrapping Up

Design thinking is crucial in any organizational setting in making sure that employees sync properly with the technology in place. This will go a long way in improving their productivity.

5 Disruptive Technologies for the Enterprise: What are the Implications?

[Apr, 16, 2014] |
Tags:

Disruptive technologies such as hand-held devices, cloud computing and social media are rattling the foundations upon which traditional businesses are built. Enterprise customers have grown smarter at ensuring the latest technological trends work in their favor. Everyone is trying to zero in on their core competencies by employing commodity services to run their business.

Likewise, enterprise application vendors need to zero in on their core competencies and enhance more value to the businesses of their clientele by leveraging standards-based commodity services, such as IaaS and PaaS, provided by leaders in those segments (e.g. Amazon EC2, Google Cloud Platform etc.).

What else enterprises need to do is learn to adopt new and emerging technologies such as cloud, utility and social computing to build on them to penetrate new market avenues.

New small and medium-sized entrants into the market are constantly challenging enterprises given their ability to rapidly turnaround and address the requirements of the customers in a cost-effective manner. Additionally, these new advancements also affect how enterprises create, deploy, and manage solutions and applications. If you take the example of Force.com, for instance, you find that it’s a common war zone for enterprise application vendors to furnish SME markets with their applications, with the new entrants mostly having an edge.

Risk Considerations When Migrating from COBOL to C#

[Oct, 16, 2018] |
Tags:

Over time, companies are migrating from COBOL to the latest standard of C# solutions due to reasons such as cumbersome deployment processes, scarcity of trained developers, platform dependencies, increasing maintenance fees. Whether a company wants to migrate to reporting applications, operational infrastructure, or management support systems, shifting from COBOL to C# solutions can be time-consuming and highly risky, expensive, and complicated. However, the following four techniques can help companies reduce the complexity and risk around their modernization efforts.

All COBOL to C# Solutions are Equal

It can be daunting for a company to sift through a set of sophisticated services and tools on the market to boost their modernization efforts. Manual modernization solutions often turn into an endless nightmare while the automated ones are saturated with solutions that generate codes that are impossible to maintain and extend once the migration is over. However, your IT department can still work with tools and services and create code that is easier to manage if it wants to capitalize on technologies such as DevOps.

Narrow the Focus

Most legacy systems are incompatible with newer systems. For years now, companies have passed legacy systems to one another without considering functional relationships and proper documentation features. However, a detailed analysis of databases and legacy systems can be useful in decision-making and risk mitigation in any modernization effort. It is fairly common for companies to uncover a lot of unused and dead code when they analyze their legacy inventory carefully. Those discoveries, however can help reduce the cost involved in project implementation and the scope of COBOL to C# modernization. Research has revealed that legacy inventory analysis can result in a 40% reduction of modernization risk. Besides making the modernization effort less complex, trimming unused and dead codes and cost reduction, companies can gain a lot more from analyzing these systems.

Understand Thyself

For most companies, the legacy system entails an entanglement of intertwined code developed by former employees who long ago left the organization. The developers could apply any standards and left behind little documentation, and this made it extremely risky for a company to migrate from a COBOL to C# solution. In 2013, CIOs teamed up with other IT stakeholders in the insurance industry in the U.S to conduct a study that found that only 18% of COBOL to C# modernization projects complete within the scheduled period. Further research revealed that poor legacy application understanding was the primary reason projects could not end as expected.

Furthermore, using the accuracy of the legacy system for planning and poor understanding of the breadth of the influence of the company rules and policies within the legacy system are some of the risks associated with migrating from COBOL to C# solutions. The way an organization understands the source environment could also impact the ability to plan and implement a modernization project successfully. However, accurate, in-depth knowledge about the source environment can help reduce the chances of cost overrun since workers understand the internal operations in the migration project. That way, companies can understand how time and scope impact the efforts required to implement a plan successfully.

Use of Sequential Files

Companies often use sequential files as an intermediary when migrating from COBOL to C# solution to save data. Alternatively, sequential files can be used for report generation or communication with other programs. However, software mining doesn’t migrate these files to SQL tables; instead, it maintains them on file systems. Companies can use data generated on the COBOL system to continue to communicate with the rest of the system at no risk. Sequential files also facilitate a secure migration path to advanced standards such as MS Excel.

Modern systems offer companies a range of portfolio analysis that allows for narrowing down their scope of legacy application migration. Organizations may also capitalize on it to shed light on migration rules hidden in the ancient legacy environment. COBOL to C# modernization solution uses an extensible and fully maintainable code base to develop functional equivalent target application. Migration from COBOL solution to C# applications involves language translation, analysis of all artifacts required for modernization, system acceptance testing, and database and data transfer. While it’s optional, companies could need improvements such as coding improvements, SOA integration, clean up, screen redesign, and cloud deployment.

training details locations, tags and why hsg

the hartmann software group advantage

why take CompTIA Training with the hartmann software group?

A successful career as a software developer or other IT professional requires a solid understanding of software development processes, design patterns, enterprise application architectures, web services, security, networking and much more. The progression from novice to expert can be a daunting endeavor; this is especially true when traversing the learning curve without expert guidance. A common experience is that too much time and money is wasted on a career plan or application due to misinformation.

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.
1. We have provided software development and other IT related training to many major corporations in Germany since 2002.
2. 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 CompTIA programming
Get your questions answered by easy to follow, organized CompTIA experts
Get up to speed with vital CompTIA 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…

learn more

page tags

what brought you to visit us

Leipzig, Germany CompTIA Training , Leipzig, Germany CompTIA Training Classes, Leipzig, Germany CompTIA Training Courses, Leipzig, Germany CompTIA Training Course, Leipzig, Germany CompTIA Training Seminar

training locations

Germany cities where we offer CompTIA Training Classes

·Munster · Berlin · Karlsruhe · Dusseldorf ·Potsdam · Augsburg ·Duisburg · Essen · Bonn · Erfurt ·Nurnberg · Koblenz ·Magdeburg · Furth · Stuttgart · Kassel ·Munich · Braunschweig ·Dortmund · Wuppertal · Dresden · Hamburg ·Freiburg · Wiesbaden ·Chemnitz · Kiel · Mannheim · Saarbrucken ·Frankfurt · Leipzig ·Bielefeld · Lubeck · Bremen · Cologne ·Heidelberg · Rostock ·Osnabruck · Hannover

CompTIA Training Classes in Leipzig, Germany

Learn CompTIA in Leipzig, Germany 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 CompTIA related training offerings in Leipzig, Germany: CompTIA Training

CompTIA Training Catalog

subcategories

Cloud Classes

Linux Unix Classes

Course Directory [training on all levels]

Blog Entries publications that: entertain, make you think, offer insight

training details locations, tags and why hsg

Interesting Reads Take a class with us and receive a book of your choosing for 50% off MSRP.