The only serious, as in customer affecting, bug I never git fixed was an indexing bug that caused an exception requiring manual intervention by one of us.

Despite going at it for many years I never found the root cause before I left the company.

The reason it was so difficult was that it only occurred every second month or less and with different customers.
It was also not triggering directly when the error occurred but a while later once the error had caused accumulated errors until one value got negative.

Also, it was a combination SQL, backend code and frontend js and the time from initial error until an invalid value could be hours, days or even weeks.

And we never ever managed to replicate it our self and found no common pattern between occasions.

We think it was some kind of race condition when updating the db that caused duplicate values or a hole in the index series (db transaction or db index was not an option for various reason that would require a redesign of the central tables and most if the central code).

This then grew into multiple error on consecutive updates until one f them resulted in a negative number that then caused a regex in js to fail.

One of my worst WFT moments was just over 2 years ago.

A former colleague had been tasked with “upgrading” our solution for handling customer specific CSS on our platform for building newsletter emails.

He had been with us for about 5 years and ported most of the front end gui over that time from classic asp to .net and C#.

This work started in November and with a pause over dec-mid jan for high season and Christmas leave he continued.

In the beginning if mars we had the first of multiple WTF on that when I realized that his solution required a lot of special CSS or rather LESS, more than the a actual HTML for the template, and all was custom less rules that was very hard to understand.

We found that he actually never really understood how LESS worked and had tried to do things in a very backward way. Another colleague jumped in and manage to clean it up a bit so it got down to manageable levels.

Then in the end of Mars came the next bigger WTF. This is a newsletter building application. Turns out the new LESS based solution was entirely dependent on the js version of LESS and only worked when running in the browser. Guess what, the email send engine is not a browser and css classes and rules generally does not work in emails.

The new solution was impossible to integrate with the part that built and sent the emails without some very heavy rework.

Oh, and it was also completely incompatible with 12 years of old newsletters and customer templates that just did not work.

And of cause, he had not shown any of this in code reviews but rather just merged it part by part to the new version branch interleaving it with 5 months of other work.

He left the company short after.

Personally the coolest was the program I built for my fathers use on his job.

It was my first to be used commercially in the real.

That was a very big thing, I was 17 at the time an used turbo pascal 5.5 and he used it to compute how well all machinery was doing, they rented out diggers and other construction equipment to construction sites and manually compute this with a calculator took up to three days. (This was 1987 so there was not very many ready made programs for business, you often had to build your own)

With this program he had it done in around 30 minutes.

The next best was recently when I got my raft distributed consensus cluster server working. Its a little bit like zookeeper.
Building that purely from the research paper was rewarding but a bit of a challenge.

A colleague was doing configuration on a server and needed to restart the network card.

So he clicked disable it, just to notice that his remote session died ...

Now where can we get a cab?

Outlook and word for html rendering.

I know it was a business decision but its been a pain since 2007 and still is.

Around 27 hours at new customer location.

They had a server failure due to incompetence.

They had fired their own IT guy and called us 6 months later because the server stopped responding.

First diagnostic. 2 drives are dead in a raid 5 with one hot spare. Raid controller then proved to be broken once the disks was replaced.

Waiting for new raid controller and installing.

Backup non existing, no one changed dat tape during the 6 months without IT. The tape was just a transparent plastic band, no media left.

Raid config is stored in static ram on controller, no backup!

Several hours in tech support to find out how to rebuild raid config from existing disks.

Proves to be impossible to rebuild raid set due to some checksum failures.

More hours with support to enable some diagnostic read only mode to mirror low level content to external drive.

Then many more hours to copy parts of the tree until it gets an error, restart after that and go on.

In the end we got around 70% back.

During this time I manage to be in contact with the raid manufacturers all support centers, one in europe, one in the us and one in Taiwan, switching each time one if them closed for the night.

The customer later declined a steady support contract due to us being to expensive ;)

Some just don’t want to learn.

20+ years ago we got a contract to replace an old home grown system for managing rented equipment for a company with offices in two countries with a new standard system.

I was tasked with building a few addon modules to handle import and reporting that the standard system lacked.

Over the course of 8 months and multiple trips to their head office for on premises development along side their people that knew how it should work (there was a lot of waiting for info so it was not 8 months of actual work) we finally was ready to present the finished solution.

After about one hour of demonstration their boss questioned why we did not demonstrate the connection to their corporate group accounting system ...

“Corporate group accounting?”

After some confused discussion it turns out that in one of the first meetings the sales person had they had mentioned this accounting system and that all accounting info was to be exported there.

This requirement was never listed in the specifications we got and looking into it it turned out that the standard system did not support such exports at all.

In the end we had to throw it all away as it proved impossible to get that info out of the system (which was not of our design).

We barely avoided having to repay all fees as their people had approved the specification but standing there without a clue to what he was asking for was a very scary experience, thinking “how could we miss this?”

Finally I could get the correct computer :)

Just missing the raised arm for the screens instead of desk stands

(ok,my real desk is not transparent but it was to cool to not take ;) )

Reading another rant about scrolling and decimal values I felt an urge to write about a bad practice I often see.

Load on demand when scrolling has been popular for quite some years but when implementing it, take some time to consider the pages overall layout.

I have several times encountered sites with this “helpful” feature that at the same time follows another staple feature of pages, especially news sites, of putting contact and address information in the footer ...

Genius right :)

I scroll down to find contact info and just as it comes in view new content gets loaded and pushes it out of view.

If you plan to use load on demand, make sure there is nothing below anyone will try to reach, no text or links or even pictures, you will frustrate the visitor ;)

The rant I was inspired by probably did not do this but its what got me thinking.
https://devrant.com/rants/1356907/...

Embedding private encryption key in production javascript file and fetching third party session token client side.

The hitchhikers guide to the galaxy is guiding spacex starman to the stars :D

I love it ♥️

When the company my mother worked for was arranging computer courses and could not leave the computers in the borrowed classrooms.

They brought them home and I got to play with them :)

Sinclair ZX80 with 512 bytes of RAM (no hard drive, diskette or CD).

This was 38 years ago ;)

Not really doubt my skills but definitely feeling inferior ;)

Reading stuff like this :

https://github.com/kevin-montrose/...

My parents have a very good grasp of what I do.

The first computer I got to try was one of the educational computers used for courses arranged by the company my mother worked for and my father studied programming before me ;)

There have been many occasions over the years.

The first was playing with a Sinqlair zx80 and getting it to print 0 instrad if syntax error ;)

The latest probably was when I started to understand react.js.

Answered a job ad in our morning news paper and got an interview.

After 2 hours or question I got an offer to try it for 3 days and I have been here since then, soon 25 years ;)

Depends on the project.

If it is a full application I usually start with what information it will handle.
Then either sketch out some database or some pages depending on how much info I got and if I got any good examples.

The less info I have, the more I try to focus on use cases and workflow to try to figure out what data will be needed.

But for more niche projects, like supportive library, ex parsers, I either mock some test in linqpad or look for similar examples online to flesh out the idea.

But I tend to very quickly fill out the basic shape and try to get something that can be tested.

Then I can find if I need to rethink it.

Years ago we had a visit from a startup company developing a firewall and I got the chance to talk with one of their devs.

He explained the subtleties of security holes in websites and after I said something about our site being secure thanks to being behind a firewall he gently asked what would happen if he entered a specially crafted test into one of the text fields ... and he gave an example ...

I got a chill, went back to my seat and traced what it would do ...

That was when I learned about sql injection and his example would have killed the DB :/

Before going home I designed a way to secure the input which I then refined over a few days.

We still use that today after 17 years.

That one single sentence really showed to never be to proud of our security and I realized how vulnerable our site was.

ABC 80.

It was a Swedish computer in the 80s.

Used basic as main shell like c64 but its editor was worse than edlin if any one remembers that.

You could not use arrow keys to go to a line to change it but had to type a command like edit 80 to retrieve the line in an editor prompt.

It also lacked a lot of common basic commands.

It got me my job :D

And I cant imagine life without.

The worst was an open source project I tried to look at.

It was written in Turbo Pascal.

I am not sure, never really got so far, but it looked like it was one single class with hundreds of methods and hundreds of instance fields for data.

Almost no data objects, if it needed for example 4 sets of 6 variables it had 24 instance fields and in some instances 4 different sets of methods for accessing said variables.

Around there I stopped looking ;)

Using mongodb for one product

A colleague as experimenting with elastic search (I think it was).

It installed a proxy around the collection to get all events for the external search storage.

Worked well, but it was just a test so once done we removed it

But thats where it got scary.

When we removed the proxy through the search dashboard it dropped the underlying collection of live data!!!

A collection it did not create.

Hows that for bad UI.

Always experiment on a separate db server.

Before shutting something down, verify that its the right one ;)

A colleague was testing some performance setting on a server and needed to restart the network driver so he disabled it and was going to enable it when the remote session died ;)

Fast 30 min trip to the datacenter to enable network card.

If an AI gets advanced enough to not require human support it will also be advanced enough to either just pamper us, or replace us.

But I think that long before that we will have neural interfaces that brings us to the next level so the AI will be part human ;)

Todays best work related question.

How is the stock of ice cream in the fridge?

We are a cloud application provider ;)

I started out on a Sinclair ZX 80. It has just 512 bytes of ram and you had to use a function button together with a key for each command since it did not have enough memory to keep the source in memory ;)

I attended few basic courses and then went on to hold them.

After a year there was suggestions of starting pascal courses so during the summer I read up in turbo pascal 5.5 but since the summer home did not have electricity I had to do it all theoretically for the first month before getting to try it out.

I got to try visual basic when doing school practice with Microsoft but the name was not set by then as it was a few months before the release.

Thats also where the more professional programming got going even though I did one pascal program that was used professionally before that.

My first dev was a small pascal application that my dad used in his job to calculate profitability of their rental machines.

Adding up interests, workshop costs and salaries an finally splitting all shared costs according to each items turnover.

Before this my dad did this by hand using an calculator with a paper printout and it usually took around 3 days with interruptions.

With my application he entered the numbers in a grid like interface and all fixed costs in a settings view and hit calculate. Took around 30 minutes.

And if he got updated figures he just loaded the monthly figures from file, changed as needed and got the new numbers in less than 1-2 minutes instead of starting all over.

This was 1987 and personal computers was just finding its way into business.

Well I dont have any worst teacher, I have been the teacher more than the student but I have a related.

Had economics last year of the equivalent to college.

We should find the optimal volume of products between 2 products requiring the same parts in different amounts.

Simple crossing point of two straight lines.

He failed our solutions because we did not draw a diagram.

Turns out he did not know of the straight line equation and did not understand how we got the solution without measuring with a ruler!

Disable email notifications.

Checking email only 3-4 times during the day saves a lot of concentration.

The stranges computer error I have seen.

When modems still was the way you communicated I worked with support.

We where the general distributor for TDC's PCCard modems.

One day we got a computer with modem with intermittent problems (worst kind).

After much trial and error we found that stroking the computer lightly in the top right corner made the modem work perfectly :)

Cause will be reviled later :p