If you are wondering if you should move from a traditional Waterfall development methodology to something new, but can’t pick between Kanban and Scrum, here is some information that might help you pick a new path.
Kanban is a simple methodology that focuses on the tasks your team is currently performing. The tasks are displayed to all participants so you and your team can track the progress and easily see what tasks are currently active. A good practice is to organize your development process using a Kanban board to show the status of each task, from “to-do”, “in progress”, “testing”, “ready for release”, and finally “released”. This simple methodology gives the team more flexible planning options, a clear focus on specific tasks, transparency on what is coming next, and a faster output by helping them focus on just a few tasks at any one time.
Continue reading “Kanban vs. Scrum”
Congratulations, you have found a new job as an IT Manager. This new job could be leading a development team, managing a group of developers, or any other management position in the IT group. How you approach your first day at the new company will make a huge difference, putting you on the path to success or making your new role a struggle. You may have been promoted to a management position at your last company, so you might not have any experience starting at a new company as a manager.
Continue reading “10 Things An IT Manager Must Do On The First Day”
If you have attended any classes or seminars on leadership or management, you have been trained on how to manage people and time, but you probably didn’t get much content on how to actually be a leader of people. Leadership is primarily providing an example of how you want people to behave by demonstrating integrity, high self-esteem, and overall confidence in purpose.
If you are interested in becoming an effective leader, look to demonstrate these skills to persuade and guide your team.
Continue reading “13 Skills Every Manager Needs”
Network design starts with creating a secure network infrastructure. While it is assumed that network design processes are obvious when it comes to placement and configuration of routers, firewalls, and switches it can often be helpful to document some of the best practices for the less experienced people that might be tasked with this process at their company.
Remember that having an established procedure and setting realistic expectations allow you to provide some consistency into your IT processes. Consistent processes tend to be repeatable and reliable, which also means you reduce the chance of surprises and security headaches.
Firewalls – Generally speaking you want a firewall placed between network segments that require a high degree of security and to keep unauthorized users off your network. This is easily demonstrated when talking about the connection between your company network and the general internet. Since you don’t want uncontrolled traffic between those two network segments, you implement a firewall. A firewall is designed to block all traffic except the specific traffic you wish to allow. You should verify your firewall has the latest vendor updates applied, all unused ports and protocols are blocked by default, and Intrusion Detection is enabled at the firewall.
Continue reading “Network Design Security Checklist”
Spectre and Meltdown Vulnerabilities
Modern CPUs that use of speculative execution has led to the vulnerabilities now known as Spectre and Meltdown. “Speculative Execution” means that if the CPU is processing instructions A, B and C, it might execute instruction B before it has the results of instruction A. This vulnerabilities potentially allows malicious software to read what should be protected memory on an unprotected computer system, allowing access to sensitive data such as passwords, encryption keys, or even cached data like the SQL Server buffer pool. Since speculative execution is intended to boost CPU performance, removing this feature will likely impact SQL Server performance by making queries run as much as 30% slower.
Continue reading “Spectre and Meltdown Impact on SQL Server”
Generally speaking, Blockchain is the digital and decentralized ledger that records transactions. Technically it is an algorithm and distributed data structure for managing electronic transactions without a central administrator. This makes it perfect for transactions among people who know nothing about one another. It was originally designed for the crypto-currency Bitcoin, and was initially driven by the rejection of government-guaranteed money and expensive bank-controlled payment transfers.
Continue reading “Blockchain Technology in Plain English”
To understand SQL Server index fragmentation, you have to first understand how SQL Server stores data. You may already know that SQL Server stores data on 8KB data pages, and that eight contiguous data pages form an extent. Each data page in both in clustered or non-clustered indexes contains data and pointers to the next and previous pages.
As data is added to a table, the index data must be saved to a data page. If there isn’t enough room on an existing page, the SQL Server engine will create a new data page to store the data, but it must also adjust the pointers on the existing data pages to reflect the new sequence of the impacted data pages. This also means that a new extent might have to be created. These new objects may be stored in a completely different part of the storage drive. This causes both database and disk fragmentation, which can make performance an issue over time.
Continue reading “Understanding SQL Server Index Fragmentation”