760 karma · joined January 5, 2009
The piece of code in question had a very straightforward task: look at some bytes in the input and produce a string label to be stored alongside the whole input value. There are 5 different labels tied to equal number of fixed byte sequences.
I would like to think that most people would solve this problem using an if/else or a switch statement inside a function. Instead, what we got is a group of matcher classes, a mapping of matchers to enum values representing the labels, another mapping of enum values to actual strings, and a class that actually calls those matchers and does the mapping.
I really hope this is not the DDD way and instead we just managed to find a team that's prone to massively overcomplicate solutions to simple problems.
Event after several iterations of giving it error messages and writing explanations of what's not working, it didn't even get past the first issue. Sometimes it would agree that it needs to fix something, but would then print back code with exactly the same problem.
This is in an area where night-time winter temperatures hover in the -5°C range, occasionally dropping to -10.
The old house was around 30 years old, with fairly thin insulation (5 or 7cm was pretty standard back when it was built), and had an oil burning furnace for heating.
I switched to Playwright 6 months ago - I'm much happier now and the switch also allowed me to delete 3/4 of the helper code that I needed before.
There are two features I really miss from jEdit:
* "dumb" autocomplete that will include any word in any open buffer, even if it's a different type (html/css/js). VSCode kindo of has word based autocomplete, but expected matches are just not there on third of teh time.
* HyperSearch (search result in the sidebar) when searching in the current buffer only. So much better than having one search mode for single buffer, and a completely different one when serching through multiple files.
Another thing she would store for the winter were whole corn plant stems, arranged in a teepee-like structure around a tree trunk. The empty space between the trunk and the corn made a favorite hiding place for both us the children, as well as her chickens.
It will come as a surprise to many people, but it's quite possible to lose a ton of money on a toxic client who is paying you millions. Avoid such "white elephant" clients at any cost. And really, the last thing you need in your life is getting dragged into some huge conglomerate's internal politics.
I never worked with Singapore Airlines, but people who have experience with them tell me they're even worse in the sense that they allegedly have a policy of not paying for software - you get to give them free stuff in exchange for being able to list them as a client. Huge software companies can afford to do that; your growth stage startup probably can't.
I discovered through trial and error that returning image bytes directly would incur this ever increasing overhead, btu creating a binary buffer and returning that would not. It was just a pet weekend project, so I never did discover what was causing the issue.
* Company A has a product that practically sells itself - it has been joked that sellers are "just accepting orders" from prospective clients. At that company the commision rate is just 4% (used to be 8%). Most sellers are fine with that because it's easy money.
* Company B is not having such an easy time selling their product - at that company the commision rate is a whopping 30%.
While it's great to have some ballpark figures, you also need to realize that you may need to (or be able to) pay your sellers al lot more/less, depending on your specific situation.