Anti Pattern Puns

I came across this in the wild and I have no idea what they are talking about. I am fairly fresh out of school and have only been in a DBA position for a year or so now, so I'm trying to see if this is a gap in my knowledge and if so, how I can learn more about it.

Text: Q: CSV is a known \"anti-pattern\" in the data interchange/interoperability realm. Since the LCB is defining a data-specification, can we use a modern format? A: At this time, submission is by .csv format only.

Any good resources for more current database antipatterns or best practices? (I saw a thread here from like 9 years ago recommending Joe Celko's books, but the most recent of those is from 2014?)

In class, and just in general, we were required to import/export data between a variety of file types including .csv with never a mention of .csv being something to avoid. Are .csv files really antipatterns? I am guessing they mean json as a modern format?

More info, the data in question is in a *RDBMS database.

*edited to relational database as my brain originally was like opposite of noSQL obviously is SQL

This is a pretty good article for a beginner like me, but also applies to other languages that I know: https://threedots.tech/post/common-anti-patterns-in-go-web-applications/. You might find it interesting. Thanks to u/aguilasolige for sharing his list of blogs to read.

Here it is: Server-side code that cannot execute on developers' local machines.

I've seen this time and again in my career, often because the server is Linux and the developer machines are Windows (but no effort is made to look at virtualization solutions).

As a result of this anti-pattern

• unit testing, or any automated testing, is impossible
• debugging consists of adding logging statements, and good lord is the codebase littered with them
• the benefits of IDEs are lost (in one incarnation I saw, developers used simple text editors because IDEs simply could not be coaxed into seeing the source code as a project)
• code quickly becomes an exponential mess because nobody knows what's going on

I'd rather leave the tech industry entirely than work with such an incompetently designed system. Yet, I have never seen this discussed much despite it's common occurance.

My first question at the end of any interview is "can your code run 100% on developer machines?" If the answer is negative, I bolt.

UPDATE: I left out a critical piece about why this problem occurs. The ultimate problem is the code is tightly coupled to an application server like JBoss or Tomcat. None of the code can obtain context to execute outside the application server so unit tests are impossible.

In season 12 the ritual weapon was a sniper, then we got anti barrier sniper. In season 13 the ritual weapon was a GL, then we got unstop GL. In season 14 the ritual weapon was a fusion rifle, then we got unstoppable fusion rifle. This season’s ritual weapon is a rocket launcher, maybe in the first season of WQ we get anti-champion rocket launchers and with that an anti-champion Gjallahorn.

It looks to me that interior mutability is a thing you should use carefully and only in the cases where it's really needed. Could anyone point me to good examples of replacing Rc<RefCell or just RefCell with better code? I.e. PRs, articles, projects which implement non trivial things without it.

Fire trucks and Ambulances are covered with the stuff. It starts shiny but gets very dull. A lot of the new stuff is coated and the existing polishes remove that coating and make it look awful... Anyone have any tips or techniques?

The company I work for have recently switched to creating microservices. So breaking up some existing monolithic applications into microservices and all new applications are now being designed as microservices.

One thing I have noticed is that the choice of database for every microservice is MongoDB. I understand its benefits; quickly get it up and running and useable, NoSQL will accept any old document etc.

However, I never see a relational database like Postgres being used for each microservice. Even when the schema is quite complex and a relational database may arguably be more appropriate.

Are NoSQL databases meant to be the go to databases for microservices?

So I need a single service bus client which has multiple queues.

This is what I've come up with.. using DI etc as well.

public interface IQueueService
{
    Task SendAsync(LoginMessageQueueModel loginMessage);
    Task SendAsync(NotificationMessageQueueModel loginMessage);
}
public class QueueService : IQueueService
{
    private readonly ServiceBusSender _loginQueueSender;
    private readonly ServiceBusSender _notificationQueueSender;
    public QueueService(ServiceBusClient _client)
    {
        _loginQueueSender = _client.CreateSender(Constants.LoginQueueName);
        _notificationQueueSender = _client.CreateSender(Constants.NotificationQueueName); 
    }

    public async Task SendAsync(LoginMessageQueueModel loginMessage)
    { 
        await _loginQueueSender.SendMessageAsync(loginMessage);
    }
    public async Task SendAsync(NotificationMessageQueueModel message)
    { 
        await _notificationQueueSender.SendMessageAsync(message);
    } 
}