• 0 Posts
  • 31 Comments
Joined 1 year ago
cake
Cake day: June 14th, 2023

help-circle







  • It seems like people aren’t reading the article and just downvoting.

    So here’s another snippet from the article which shows you the kid needs serious help:

    Kurtaj leaked 90 videos of GTA VI gameplay footage last September while out on bail for hacking Nvidia and British telecom provider BT / EE. Although he stayed at a hotel under police protection during this time, Kurtaj still managed to carry out an attack on Rockstar Games by using the room’s included Amazon Fire Stick and a “newly purchased smart phone, keyboard and mouse,” according to a separate BBC report. Kurtaj was arrested for the final time following the incident.


    Like come on man, how many chances is enough? If there’s no real consequences for people’s actions, they just do whatever they please. Actions have consequences.








  • Transactions are the safe way of doing it.

    You can also return * to see the changes, or add specific fields.

    Like for example:

    Begin; Update users Set first_name=‘John’ Where first_name=‘john’ Returning *;

    Then your Rollback; Or Commit;

    So you’d see all rows you just updated. You can get fancy and do a self join and see the original and updated data if you want. I like to run an identifying query first, so I know hey I should see 87 rows updated or whatever.

    Haven’t had any issues with table locks with this, but we use Postgres. YMMV.



  • Yeah this sounds like more of an issue with how the company interacted with the clients and the expectations that are set.

    My comment also isn’t helpful, just saying the situation sucks when you’re the employee dealing with the situation.

    In my view, from some years in customer service and tech, you either need to develop a more robust system to prevent this behavior, or start slapping clients on the wrist for this behavior. Otherwise they will continue to walk all over your company. The c-levels don’t care because the customer is happy because shit gets done and they get paid. However, if a client runs into an issue due to their negligence and you’re not there immediately to fix it they either learn to prevent the issues themselves or switch to another service.

    There are points where you may need to grin and bear it, but it’s not sustainable as you mentioned.

    My favorite issue that’s been happening far too frequently is my company takes on a new client or a new request from an existing client without confirming that the software can do the request. And then right before their deadline (1-2 days typically) they go “oh this value isn’t what we expected” or “can we provide X to the client”.

    We sure can fix that, but it won’t magically happen in your expedited timeframe. Failure to plan on your end does not constitute an emergency on my end.