8 ms·
It may be a "one-liner", but it's the kind where the engineer had to have broad and detailed knowledge about the system and how it works. Well done!
by programmarchy 3y ago
It may be a "one-liner", but it's the kind where the engineer had to have broad and detailed knowledge about the system and how it works. Well done!
- kevincox 3y agoThe classic: 1. Doing the thing $5/h 2. Knowing what thing to do $500/h
- greiskul 3y agoYup. One of the most complex bug I ever fixed was caused by a race condition. It took me 2 weeks to investigate and fix it. The final result was a couple of lines (like 5).
- hexo 3y agoHow much have you been paid for it? $4k? I'd be brutally laughed at in this "awesome" country for that. Some just cannot understand it. How do you get them actually pay for that time? Thats a mystery for me.
- tracker1 3y agoHad dealt with a similar issue, as well as an issue where all configuration variables was loaded from a database into an in-memory table, and that table was queried with a sql-like structure like a thousand times over a single web request stack (login request was like 25-30s). I swapped it out with a hash table, and that knocked the login request to under 10s, and 9.5s of that was an external system outside my control. On the race condition, that was actually pretty easy to diagnose and solve, replaced the static property with a local getter/setter using the request context to store the value (asp.net 2.0).
- nonethewiser 3y agoSo many bugs are like this. Spend 1 or 2 days on it and then ship a 1 line change.