SoyViking [he/him]

  • 0 Posts
  • 75 Comments
Joined 5 years ago
cake
Cake day: November 4th, 2020

help-circle




  • They determine a lot through pricing and decision on availability.

    People don’t like getting ripped off or paying more than they have to so people, myself included, buy more of whatever they happen to have on sale this week. At our house a lot of decisions on what to have for dinner start by looking through the weekly offers page on the supermarket’s app which influences our diet. For instance we eat a lot more chicken than we would do if it wasn’t constantly on sale.

    Decisions to jack up prices also affect diet. For instance we used to eat a lot of ground beef and sour cream but now it has become so expensive that it is no longer worth what they’re charging so we almost never have it anymore.

    Availability is also a huge part of the way they determine what we eat. It don’t even have to be a food desert to have a huge influence, the convenience of not having to go to more than one shop alone has a huge influence. For instance I like beefsteak tomatoes a lot more for everything where you cut up the tomatoes and don’t want the watery seeds. But I eat a lot more plum tomatoes because that’s what they have at ordinary supermarkets and I would have to go to the Arab store to get the other ones which would mean I would have to spend 20 minutes more shopping.








  • I’m the guy on that airplane at the moment.

    I get specs for an external API to use in a new major feature. I begin implementing, the specs doesn’t add up because nobody paid the eastern European gig programmers to document anything. Eventually I derive plausible specs from a frustrating process of emails and trial and error.

    I implement the major feature to the specs provided by the client. The client tests in staging and requests several adjustments. I implement those, client tests again and accepts.

    The feature is pushed to production. The client finds a ton of errors because of course the rudimentary specs I managed to wrestle out of the client and the big-shot corner-cutting third party API developer didn’t describe half of the ideosyncratic data structure they send. Stuff like sending completely empty posts and expecting empty rows to be inserted in the database, sending text comments in fields intended for storing numbers instead of in the dedicated comment field. That sort of bullshit. They want to pour garbage in an have garbage coming out.

    So I had to do a ton of hotfixes directly to production. Everything have to be fixed yesterday because it is a business critical feature. It sucks. It’s a clusterfuck of cherry picking and it becomes impossible to do any sort of quality control.

    A ton of errors got introduced because nobody explained to the Eastern Europeans what the API should do or gave them the time to do it properly. I am the lead engineer on the project and I have to rush to make emergency bug investigations all the time. Most of the things the bug is that the Eastern Europeans didn’t set up their system like they were asked to or that nobody told them how it should work and just assumed they would know. I wrote more emails than code. The client pays a ton of money for all of this and nothing gets done because they rushed into this feature without planning it properly.