↓ Skip to main content

Uncategorized

Comparing SecureStrings

Comparing SecureStrings

·1 min
After writing about SecureStrings, you soon come to realise that holding the secret information you are going to have to make some comparisons at some point. For example, if you need to check a password.

Uncle Bob On Coding Standards

·1 min
It’s important for a team to have a single coding standard for each language to avoid several problems: A lack of standards can make your code unreadable. Disagreement over standards can cause check-in wars between developers. Seeing different standards in the same class can be extremely irritating. UncleBob wrote this:

GitHub for web Designers

·5 mins
Unless you’re a one person web shop with no team to collaborate with, you’ve experienced the frustration that goes along with file sharing. No matter how hard you try, when multiple people are working on a single project without a version control system in place things get chaotic.

What is the difference between running in Debug and Release mode?

·4 mins
Is the only difference between Debug and Release configurations that Debug have the DEBUG constant defined, and Release produces the Optimize code? Are there performance differences between these two configurations. Are there any specific type of code that will cause big differences in performance here, or is it actually not that important? Are there any type of code that will run fine under the Debug configuration that might fail under Release configuration, or can you be certain that code that is tested and working fine under the Debug configuration will also work fine under Release configuration. The C# compiler itself doesn’t alter the emitted IL a great deal in the Release build. Notable is that it no longer emits the NOP opcodes that allow you to set a breakpoint on a curly brace. The big one is the optimizer that’s built into the JIT compiler. It does make the following optimizations:

Automation Testing

·1 min
Automation Fesability.docx (259.00 kb) Automation tools and estimation.docx (16.94 kb) EXCEL- SHEET for estimation.xlsx (21.06 kb)

Using the WebGrid in MVC correctly

·6 mins
I know the WebGrid is a basic Grid control, but sometimes you are constrained with what you can use with a customer and WebGrid is by default from Microsoft so it is safe to use and does not require any unknown third party tools to be installed.

Bug Process

·2 mins
Background Note: Click the process for a larger version. When a bug is first created it is assigned a nominal story point value of 1. This value is intended to cover the investigation phase of the bug only (or a fix if it’s found to be a small issue). Having a story point value against the bug (even if it only covers investigation initially) means that we can allocate each bug into a sprint along with other backlog items and gives a window of time to investigate the problem. The outcome of this stage should be either: Bug resolved; should only occur with small bugs where the issue was found, fixed and re-tested within the allocated tasked hours Further investigation required; in which case the story-point value of the bug should be increased to indicate that the problem is very complex and was not able to even be progressed during the first pass through the stage Investigation completed; where the problem has been documented within the bug item and a number of tasks (with associated hours assigned) have been created which detail how to resolve the problem Bugs which have not progressed (e.g. outcome 2 in the list above) should be re-story-pointed and added back into the main backlog to progress through stage 1 again at a later date. Obviously bugs which have been resolved (outcome 1) can be marked as such and bugs which have been investigated and tasked (outcome 3) can be added back into the product backlog for assigning to a future sprint. Note: The important point to note about this phase is that it should be considered time-boxed based on what time is allocated to the tasks created for the bug at sprint planning – based on the default story point value and current velocity, this should be roughly around 3 hours total. Stage 2 – Fixing Note: Click the process for a larger version. Bugs which enter this stage should have already been through the first stage of investigation at least once and should have appropriate tasks against them which detail what needs to happen to resolve the problem. Since each bug should have been through the first stage of analysis, we should know enough at this stage to be confident in being able to both apply a fix and complete the associated tasks in the allocated sprint.

Validation from WCF layer through to MVC

·6 mins
 First off, why would you want to perform validation in the WCF layer? After a vigorous PEN test, it was noted that the validation was mainly happening at the client browser and the application required validation to occur at the business logic layer, in our case the WCF layer.

Use Case templates

·1 min
Writing Effective Use Cases – by Alistair Cockburn.pdf (420.04 kb) Use Case Template v0.1.docx (302.38 kb)

How to perform JavaScript Unit Testing

·3 mins
Following the TDD approach when you are working with MVC it is quite easy to produce Unit Tests that are based on the MVC Controllers, with more and more business logic appearing in the User Interface by using libraries such as jQuery it is becoming more important to perform Unit Testing on JavaScript.

files

·1 min
TalentCubed.zip (3.34 mb)

Switching from iPhone to Android

·5 mins
The iPhone is the top smartphone, but some Android rivals like the Galaxy S III are very attractive, and they’re available in large sizes that the iPhone is not. Plus, they support cool technologies Apple doesn’t support.

Disable Shut Down on your Server

·1 min
When you are connecting via a remote connection to a server I find the Shut Down is far far to close to the log off, and if you hit the Shut Down by mistake it can be a devil to get the remote machine to power back up and may require someone to visit the machine to hit the power button.

How and setup and got my Gadgeteer to work

·3 mins
This is a quick start guide for .NET Gadgeteer and the FEZ Spider Kit. It includes instructions for the installation of necessary software and drivers of the Gadgeteer platform as well as for the first Gadgeteer program. 

Going in to Space

·1 min
 Hello Kitty in space https://www.youtube.com/watch?v=5REsCTG4-Gg&feature=player_embedded

Hacking at its best with DNS

·4 mins
I received a tweet yesterday from @gravax who was the Epic Hack of the Day, so just check this out which is pretty cool tracert -h 99 216.81.59.173 You get back 12 * * *

Avoid, Find and Fix ASP.NET Performance Issues

·1 min
Following on from my articles on producing smarter code I have come across “50 ways to Avoid, Find and Fix ASP.NET Performance Issues” by RedGate, won’t say it is the best advise but still gives some good tips on how to improve performance.