Forgot your password?
typodupeerror

Comment: Re:Weak (Score 1) 310

by gbjbaanb (#46778623) Attached to: Switching From Sitting To Standing At Your Desk

eh?

Assuming intelligent design for a moment, we were designed for stuff our ancestors were used to - running about and generally standing up.,

We were not ever designed to slouch in front of a TV/monitor with a little tool in our hands waggling it up and down (or side to side) pressing buttons.

So,much as I really don't care if ID is true or fantasy, citing proof of our sedentary lifestyles is not and argument against it.

Comment: Re:Are you still partying like its 1999, or what? (Score 2) 289

by gbjbaanb (#46777525) Attached to: Ask Slashdot: System Administrator Vs Change Advisory Board

oh god Remedy....I used that once.

But the concept is good- you need a 'bug tracker' where the requests for patches can be made to you, and you can then assign tot he CCB. Once they agree it, then assign it back to you for implementation.

Any dev bugtracker will provide you with this kind of audit trail - think 'requirements' for the CCB authorisation, 'development' for the implementation, 'test' for the testing. You might want to rename these though.

I'd make it web based so access is simple for everyone involved - last thing you need is a Excel based solution. I've used Mantis, or Redmine but Bugzilla would work too as would any number of web based bug/task tracker tools. Get one installed before someone on the CCB says "we'll use a spreadsheet", seriously.

Comment: Re:Not a surprise, but no reflection of O/S vs Pro (Score 4, Insightful) 132

by gbjbaanb (#46777193) Attached to: Code Quality: Open Source vs. Proprietary

are you sure about that?

unsafe
{
// srcPtr and destPtr are IntPtr's pointing to valid memory locations
// size is the number of long (normally 4 bytes) to copy
    long* src = (long*)srcPtr;
    long* dest = (long*)destPtr;
    for (int i = 0; i < size / sizeof(long); i++)
    {
        dest[i] = src[i];
    }
}

that's valid C#, all you need to do is inject something like that into the codebase and let the JIT compile it (using all the lovely features they added to support dynamic code) and you're good to get all the memory you like.

Now I know the CLR will not let you do this so easily, but there's always a security vulnerability lying around waiting to be discovered that will, or an unpatched system that already has such a bug found in any of the .NET framework, for example this one that exploits... a "buffer allocation vulnerability", and is present in Silverlight.

The moral is ... don't think C programs are somehow insecure and managed languages are perfectly safe.

Comment: Re:I have serious doubts.. (Score 2) 101

by gbjbaanb (#46764837) Attached to: Your <em>StarCraft II</em> Potential Peaked At Age 24

There is - but its very boring.

You generally look at the map from a distance, grouping your units into manageable armies. Then your entire interface looks more like a few points on a map and a spreadsheet as the relevant army stats are displayed in a grid.

This is the way real life Command and control interfaces are designed. A police 911 dispatcher will manage individual units rather than armies, but they will still need access to their stats (eg what equipment and training the unit has), their location and the location of any event (and the details of said location).

If you want to compare that to SC, you'll see it way different - much less frantic, which is important as you don't want the operator to be overwhelmed with information. You want them to see the "bigger picture" so they can plan the resource allocation effectively, calmly and with thought.

Comment: Re:Funny (Score 1) 689

by gbjbaanb (#46750729) Attached to: The GNOME Foundation Is Running Out of Money

Oh I am not a libertarian. I just point out that most people in high office are psychopaths with their own pushing ambition and lack of care for anyone who gets in the way of their own agendas.

This applies to men and women, but as the topic concerned a woman abusing her position to push her own agenda, I felt it was unnecessary to mention psycho male execs too.

Most women do like "feminine" jobs, hence the number of women in nursing, childcare and similar.

Comment: Re:Funny (Score 1) 689

by gbjbaanb (#46744981) Attached to: The GNOME Foundation Is Running Out of Money

only the "executive" women are the ones who can't hack real-world jobs. Don't belittle most women by comparing them to these self-appointed attention whores.

The fact is that most women prefer different jobs, more social ones like teaching or nursing. These are valuable jobs that have a disproportionate amount of men in them too,, there's always more calls for men in primary schools for example, but strangely never any outreach programmes for male primary teachers.

So girls don't like working in computing... so what. There are plenty other careers available.

Comment: Re:Good for devs. (Score 1) 270

by gbjbaanb (#46729319) Attached to: The New 'One Microsoft' Is Finally Poised For the Future

It is the preferred solution... unfortunately.

Try the Windows Web Services alternative (a compatible system designed by the Windows team, significantly faster and less memory intensive).

I also thought the new preferred way to write back-end services was to sue the REST toolkit that came out with VS2013 (ex codename casablanca). WCF is only still around because the ,NET devs don't have much of an alternative, that's all.

Comment: Re:ya ya.. (Score 1) 445

by gbjbaanb (#46722983) Attached to: Heartbleed Coder: Bug In OpenSSL Was an Honest Mistake

but a unit test wouldn't show this up - nobody would write a test, testing that the function worked, and start looking at external impacts of that function.

For this to be caught using testing, you'd need a fairly good coverage integration test. Unit tests are just too focussed on small things. They prove the unit works as expected, they never consider interaction with other parts of the overall system.

Simplicity does not precede complexity, but follows it.

Working...