Tag: work


0verkill (howto enjoy work properly – the geeky way)

If you ever lacked an idea on how to spend your time at work properly, here’s a fun thing to try: 0verkill – a multiplayer 2D ASCII art shooter.Hell yeah, an ASCII art shooter, you heard right! To hell with those flashy commercials claiming to be proper games!

If you’re on a Debian box (as you should), you can install it from the commandline
$ aptitude install overkill

If you’re less lucky, you can also go to the author’s homepage, download and build it yourself. The package will feature the game itself, a dedicated server and a level-editor. Plenty of room for a great many gaming sessions!

overkill2

Picture 1 of 3

Notes:
1. There were more players, but I didn’t managage to get my glorifying screenshot soon enough.
2. Beware of server lag. I played it in a screen session on a Linux VPS. I got a load average of up to 19.48, 7.16, 3.00

Comment » | personal

Disable Windows auto desktop lock

Let me start with: “I hate Windows from the bottom of my heart.”

But there’s another level of hate. I hate pseudo business proof settings in Windows even more. One of those would be the “Auto Lock”.

Anyway, if you think that your (clients) VPN – or bureau for that case – can keep up its security without the dreaded auto lock – here’s what you do:

1. Hate the auto lock


2. Right click your desktop


3. Chose screensaver

4. Uncheck “On resume, display logon screen”



5. Be

At least a little less unhappy. You’re still with Windows. You’re still doomed. But the apocalypse is a little farther away for now.

5 comments » | personal

True story – Software Engineering fail (follow up)

Funny thing – or should I say: True story!

In my most recent blog post “I want to work in a company which” I wrote about some issues of a random company. I published this article three days before news of this particular company struck me again in agony. While reading this, keep in mind that this company has no direct connection to me whatsoever.

Apparently the head of department of sales and marketing walked up to the programmers of his division. I have been told he normally would not even be seen in closer proximity of the tech department. However, this time he was obviously in pain and instantly called for a crisis-meeting.

In the meeting there were reports of working hours of the programmers, there were affronting comments on peoples’ work ethics – there even was a printout of an emergency escalation e-mail of a client. Reverse engineering of the misleading rants brought light into the programmers’ darkness. It seemed that the client was waiting for a major software roll-out. Now, while the company seemed to desperately need this client, it forgot to tell the programmers about the roll-out.

Well, what could we say? I’d call it: Software Engineering Fail.

It seems this company lacks basic release management – all they now is hotfixes. Also, there are no reviews, there is no transparent project planning, there’s no testing framework or regression testing. There is no procedure model which in combination with no apparent quality management is certain proof for failure in engineering larger scale software for a living.

What is left to do? I have heard the programmers had a meeting of their own. They talked for hours about basic and pragmatic needs for succeeding in what they are paid for: writing serious software. Seemingly they believe there is still an off-chance for the company to turn around from being solely a solutions provider for its clients while raping its own employees.

We’ll see, time will tell the truth. My personal attitude in this matter: If things won’t change quickly and those guys are not only searching for a job just to pay their rents, but also to bring joy and knowledge to their life: run for it, guys!

Comment » | personal

« Previous Entries