Web Services Training Classes in Quebec, Canada

Learn Web Services in Quebec, Canada 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 Web Services related training offerings in Quebec, Canada: Web Services Training

We offer private customized training for groups of 3 or more attendees.

Web Services Training Catalog

cost: $ 1690length: 4 day(s)
cost: $ 2090length: 5 day(s)
cost: $ 1390length: 3 day(s)
cost: $ 2090length: 5 day(s)
cost: $ 2090length: 5 day(s)
cost: $ 390length: 1 day(s)
cost: $ 1090length: 2 day(s)
cost: $ 2090length: 5 day(s)
cost: $ 1390length: 4 day(s)
cost: $ 1390length: 4 day(s)

Course Directory [training on all levels]

Upcoming Classes
Gain insight and ideas from students with different perspectives and experiences.

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

What are the three most important things non-programmers should know about programming?
 
Written by Brian Knapp, credit and reprint CodeCareerGenius
 
 
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.

 
One of the biggest threats facing small businesses right now is cyber security. Hackers have figured out that small business don’t have robust systems; therefore, they are easy for the picking. If you are a small business owner, you know how limited your resources are. As such, every dollar counts. Therefore, you can’t afford to lose customers, deal with lawsuits caused by data breaches or pay IT help staff to try to fix the issue. Below are some of the IT risks faced by your business and potential consequences. Try your best avoid them at all costs. 
 
1. Phishing 
 
This is perhaps one of the easiest ways to detect if a hacker is trying to get into your system. If you happen to receive an email that claims to be from a financial institution and asks you to provide certain data, ignore it. In fact, delete it. This is because once you make the mistake of opening such a mail or clicking the link provided, you provide a gateway for hackers to penetrate your system and steal information. For this reason, it's vital that all employees  are aware of such emails and delete them without clicking on any links.
 
2. Passwords 
 
Another way that hackers can attack a small business is by cracking system passwords. If the hackers manage to crack the password of even a single employee, they can use that person’s account to gain unrestricted access to confidential company records. Therefore, tell your workers that they should never forgo strong password creation procedures. They should take their time to create a password that can’t be easily cracked. 
 
3. Vulnerable Devices 
 
In your small business, you probably use printers, routers, and other electronic hardware to execute office tasks. Most of the time, such pieces of hardware are connected to your firm’s network. If you have not updated the software on these machines, hackers can use them to gain access to your network and steal invaluable information. Therefore, make sure that you install patches in all electronic devices connected to your network. 
 
4. Lack of Data Encryption 
 
In the modern age, you can send information through various electronic devices. Some of those machines can have inbuilt security features to protect the data while others may not have. Data from the vulnerable devices can be easily intercepted by hackers. If the information is your password, your network is no longer safe. To counter such interceptions, always encrypt your data before your send it. 
 
5. Seemingly Misplaced USB Drives 
 
Some hackers will infect a USB drive with malware and then drop it outside your offices. An unknowing worker may pick up the drive and use it on a company computer. Immediately the drive is plugged in, it releases the malware and creates a unique access point for the hacker, allowing them to steal information. To avoid such a scenario, warn your employees against using any USB drives without a proper source. 
 
 
Managing a small business means that you’re a lean, mean business machine. Often, it’s just you and a few trusted staff members. This is the reason, business owners need to have solid knowledge of where and how most important data is held. Whether it’s on site, in traditional desktops and servers, or in cloud services or mobile devices including those "BYOD" devices of your employees, in order to avoid risks, always pay attention to your enviroment. It's important to make sure that you regularly update your system, train your employees, update software and fix bugs. Often, many IT issues are caused by the smallest, almost unapparent mistakes that will affect how a program runs or a web page looks. You might not see IT as your highest priority, but in the right hands, it can become your most powerful tool for growth. 

I will begin our blog on Java Tutorial with an incredibly important aspect of java development:  memory management.  The importance of this topic should not be minimized as an application's performance and footprint size are at stake.

From the outset, the Java Virtual Machine (JVM) manages memory via a mechanism known as Garbage Collection (GC).  The Garbage collector

  • Manages the heap memory.   All obects are stored on the heap; therefore, all objects are managed.  The keyword, new, allocates the requisite memory to instantiate an object and places the newly allocated memory on the heap.  This object is marked as live until it is no longer being reference.
  • Deallocates or reclaims those objects that are no longer being referened. 
  • Traditionally, employs a Mark and Sweep algorithm.  In the mark phase, the collector identifies which objects are still alive.  The sweep phase identifies objects that are no longer alive.
  • Deallocates the memory of objects that are not marked as live.
  • Is automatically run by the JVM and not explicitely called by the Java developer.  Unlike languages such as C++, the Java developer has no explict control over memory management.
  • Does not manage the stack.  Local primitive types and local object references are not managed by the GC.

So if the Java developer has no control over memory management, why even worry about the GC?  It turns out that memory management is an integral part of an application's performance, all things being equal.  The more memory that is required for the application to run, the greater the likelihood that computational efficiency suffers. To that end, the developer has to take into account the amount of memory being allocated when writing code.  This translates into the amount of heap memory being consumed.

Memory is split into two types:  stack and heap.  Stack memory is memory set aside for a thread of execution e.g. a function.  When a function is called, a block of memory is reserved for those variables local to the function, provided that they are either a type of Java primitive or an object reference.  Upon runtime completion of the function call, the reserved memory block is now available for the next thread of execution.  Heap memory, on the otherhand, is dynamically allocated.  That is, there is no set pattern for allocating or deallocating this memory.  Therefore, keeping track or managing this type of memory is a complicated process. In Java, such memory is allocated when instantiating an object:

String s = new String();  // new operator being employed
String m = "A String";    /* object instantiated by the JVM and then being set to a value.  The JVM
calls the new operator */

The world of technology moves faster than the speed of light it seems. Devices are updated and software upgraded annually and sometimes more frequent than that.  Society wants to be able to function and be as productive as they can be as well as be entertained “now”.

Software companies must be ready to meet the demands of their loyal customers while increasing their market share among new customers. These companies are always looking to the ingenuity and creativity of their colleagues to keep them in the consumer’s focus. But, who are these “colleagues”? Are they required to be young, twenty-somethings that are fresh out of college with a host of ideas and energy about software and hardware that the consumer may enjoy? Or can they be more mature with a little more experience in the working world and may know a bit more about the consumer’s needs and some knowledge of today’s devices?

Older candidates for IT positions face many challenges when competing with their younger counterparts. The primary challenge that most will face is the ability to prove their knowledge of current hardware and the development and application of software used by consumers. Candidates will have to prove that although they may be older, their knowledge and experience is very current. They will have to make more of an effort to show that they are on pace with the younger candidates.

Another challenge will be marketing what should be considered prized assets; maturity and work experience. More mature candidates bring along a history of work experience and a level of maturity that can be utilized as a resource for most companies. They are more experienced with time management, organization and communication skills as well as balancing home and work. They can quickly become role models for younger colleagues within the company.

Unfortunately, some mature candidates can be seen as a threat to existing leadership, especially if that leadership is younger. Younger members of a leadership team may be concerned that the older candidate may be able to move them out of their position. If the candidate has a considerably robust technological background this will be a special concern and could cause the candidate to lose the opportunity.

Demonstrating that their knowledge or training is current, marketing their experience and maturity, and not being seen as a threat to existing leadership make job hunting an even more daunting task for the mature candidate. There are often times that they are overlooked for positions for these very reasons. But, software companies who know what they need and how to utilize talent will not pass up the opportunity to hire these jewels.

 

 Related:

H-1B Visas, the Dance Between Large Corporations and the Local IT Professional

Is a period of free consulting an effective way to acquire new business with a potential client?

training details locations, tags and why hsg

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 Canada 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 Web Services programming
  • Get your questions answered by easy to follow, organized Web Services experts
  • Get up to speed with vital Web Services 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
Quebec, Canada Web Services Training , Quebec, Canada Web Services Training Classes, Quebec, Canada Web Services Training Courses, Quebec, Canada Web Services Training Course, Quebec, Canada Web Services Training Seminar
training locations
Canada cities where we offer Web Services Training Classes

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