SQL Server Training Classes in Dublin, Ireland

Learn SQL Server in Dublin, Ireland 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 SQL Server related training offerings in Dublin, Ireland: SQL Server Training

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

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

Although reports made in May 2010 indicate that Android had outsold Apple iPhones, more recent and current reports of the 2nd quarter of 2011 made by National Purchase Diary (NPD) on Mobile Phone Track service, which listed the top five selling smartphones in the United States for the months of April-June of 2011, indicate that Apple's iPhone 4 and iPhone 3GS outsold other Android phones on the market in the U. S. for the third calendar quarter of 2011. This was true for the previous quarter of the same year; The iPhone 4 held the top spot.  The fact that the iPhone 4 claimed top spot does not come as a surprise to the analysts; rather, it is a testament to them of how well the iPhone is revered among consumers. The iPhone 3GS, which came out in 2009 outsold newer Android phones with higher screen resolutions and more processing power. The list of the five top selling smartphones is depicted below:

  1. Apple iPhone 4
  2. Apple iPhone 3GS
  3. HTC EVO 4G
  4. Motorola Droid 3
  5. Samsung Intensity II[1]

Apple’s iPhone also outsold Android devices7.8:1 at AT&T’s corporate retail stores in December. A source inside the Apple company told The Mac Observer that those stores sold some 981,000 iPhones between December 1st and December 27th 2011, and that the Apple device accounted for some 66% of all device sales during that period (see the pie figure below) . Android devices, on the other hand, accounted for just 8.5% of sales during the same period.

According to the report, AT&T sold approximately 981,000 iPhones through AT&T corporate stores in the first 27 days of December, 2011 while 126,000 Android devices were sold during the same period. Even the basic flip and slider phones did better than Android, with 128,000 units sold.[2] However, it is important to understand that this is a report for one particular environment at a particular period in time. As the first iPhone carrier in the world, AT&T has been the dominant iPhone carrier in the U.S. since day one, and AT&T has consistently claimed that the iPhone is its best selling device.

Chart courtesy of Mac Observer: http://www.macobserver.com/tmo/article/iphone_crushes_android_at_att_corporate_stores_in_december/

A more recent report posted in ismashphone.com, dated January 25 2012, indicated that Apple sold 37 million iPhones in Q4 2011.  It appears that the iPhone 4S really helped take Apple’s handset past competing Android phones. According to research firm Kantar Worldpanel ComTech, Apple’s U.S. smartphone marketshare has doubled to 44.9 percent.[3] Meanwhile, Android marketshare in the U.S. dropped slightly to 44.8 percent. This report means that the iPhone has edged just a little bit past Android in U.S. marketshare. This is occurred after Apple’s Q1 2012 conference call, which saw themselling 37 million handsets. Meanwhile, it’s reported that marketers of Android devices, such as Motorola Mobility, HTC and Sony Ericsson saw drops this quarter.

The original article was posted by Michael Veksler on Quora

A very well known fact is that code is written once, but it is read many times. This means that a good developer, in any language, writes understandable code. Writing understandable code is not always easy, and takes practice. The difficult part, is that you read what you have just written and it makes perfect sense to you, but a year later you curse the idiot who wrote that code, without realizing it was you.

The best way to learn how to write readable code, is to collaborate with others. Other people will spot badly written code, faster than the author. There are plenty of open source projects, which you can start working on and learn from more experienced programmers.

Readability is a tricky thing, and involves several aspects:

  1. Never surprise the reader of your code, even if it will be you a year from now. For example, don’t call a function max() when sometimes it returns the minimum().
  2. Be consistent, and use the same conventions throughout your code. Not only the same naming conventions, and the same indentation, but also the same semantics. If, for example, most of your functions return a negative value for failure and a positive for success, then avoid writing functions that return false on failure.
  3. Write short functions, so that they fit your screen. I hate strict rules, since there are always exceptions, but from my experience you can almost always write functions short enough to fit your screen. Throughout my carrier I had only a few cases when writing short function was either impossible, or resulted in much worse code.
  4. Use descriptive names, unless this is one of those standard names, such as i or it in a loop. Don’t make the name too long, on one hand, but don’t make it cryptic on the other.
  5. Define function names by what they do, not by what they are used for or how they are implemented. If you name functions by what they do, then code will be much more readable, and much more reusable.
  6. Avoid global state as much as you can. Global variables, and sometimes attributes in an object, are difficult to reason about. It is difficult to understand why such global state changes, when it does, and requires a lot of debugging.
  7. As Donald Knuth wrote in one of his papers: “Early optimization is the root of all evil”. Meaning, write for readability first, optimize later.
  8. The opposite of the previous rule: if you have an alternative which has similar readability, but lower complexity, use it. Also, if you have a polynomial alternative to your exponential algorithm (when N > 10), you should use that.

Use standard library whenever it makes your code shorter; don’t implement everything yourself. External libraries are more problematic, and are both good and bad. With external libraries, such as boost, you can save a lot of work. You should really learn boost, with the added benefit that the c++ standard gets more and more form boost. The negative with boost is that it changes over time, and code that works today may break tomorrow. Also, if you try to combine a third-party library, which uses a specific version of boost, it may break with your current version of boost. This does not happen often, but it may.

Don’t blindly use C++ standard library without understanding what it does - learn it. You look at std::vector::push_back() documentation at it tells you that its complexity is O(1), amortized. What does that mean? How does it work? What are benefits and what are the costs? Same with std::map, and with std::unordered_map. Knowing the difference between these two maps, you’d know when to use each one of them.

Never call new or delete directly, use std::make_unique and [cost c++]std::make_shared[/code] instead. Try to implement usique_ptr, shared_ptr, weak_ptr yourself, in order to understand what they actually do. People do dumb things with these types, since they don’t understand what these pointers are.

Every time you look at a new class or function, in boost or in std, ask yourself “why is it done this way and not another?”. It will help you understand trade-offs in software development, and will help you use the right tool for your job. Don’t be afraid to peek into the source of boost and the std, and try to understand how it works. It will not be easy, at first, but you will learn a lot.

Know what complexity is, and how to calculate it. Avoid exponential and cubic complexity, unless you know your N is very low, and will always stay low.

Learn data-structures and algorithms, and know them. Many people think that it is simply a wasted time, since all data-structures are implemented in standard libraries, but this is not as simple as that. By understanding data-structures, you’d find it easier to pick the right library. Also, believe it or now, after 25 years since I learned data-structures, I still use this knowledge. Half a year ago I had to implemented a hash table, since I needed fast serialization capability which the available libraries did not provide. Now I am writing some sort of interval-btree, since using std::map, for the same purpose, turned up to be very very slow, and the performance bottleneck of my code.

Notice that you can’t just find interval-btree on Wikipedia, or stack-overflow. The closest thing you can find is Interval tree, but it has some performance drawbacks. So how can you implement an interval-btree, unless you know what a btree is and what an interval-tree is? I strongly suggest, again, that you learn and remember data-structures.

These are the most important things, which will make you a better programmer. The other things will follow.

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. 

A business rule is the basic unit of rule processing in a Business Rule Management System (BRMS) and, as such, requires a fundamental understanding. Rules consist of a set of actions and a set of conditions whereby actions are the consequences of each condition statement being satisfied or true. With rare exception, conditions test the property values of objects taken from an object model which itself is gleaned from a Data Dictionary and UML diagrams. See my article on Data Dictionaries for a better understanding on this subject matter.

A simple rule takes the form:

if condition(s)

then actions.

An alternative form includes an else statement where alternate actions are executed in the event that the conditions in the if statement are not satisfied:

if condition(s)

then actions

else alternate_actions

It is not considered a best prectice to write rules via nested if-then-else statements as they tend to be difficult to understand, hard to maintain and even harder to extend as the depth of these statements increases; in other words, adding if statements within a then clause makes it especially hard to determine which if statement was executed when looking at a bucket of rules. Moreoever, how can we determine whether the if or the else statement was satisfied without having to read the rule itself. Rules such as these are often organized into simple rule statements and provided with a name so that when reviewing rule execution logs one can determine which rule fired and not worry about whether the if or else statement was satisfied. Another limitation of this type of rule processing is that it does not take full advantage of rule inferencing and may have a negative performance impact on the Rete engine execution. Take a class with HSG and find out why.

Rule Conditions

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

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