Niklas Enns

Did you know you can go DRY in Postgres table definitions – that is, define commonalities in one place and use them in different table definitions? It's like mixins, allowing you to focus more on the concepts you're introducing —the perfect example of Don't Repeat Yourself.

@unclebobmartin When extracting code into methods, we try to choose a method name that explains what the method does. Now, I have a module boundary and I think that "void accept(String data)" is a good method name, because, it hides implementation details and reduces coupling.

@gunnarmorling The flaw is in the language and it's implementation of visibility features. It doesn't distinguish between *using* a module and *testing* a module. These two purposes come with their own segregated Interfaces but the visibility keywords and the compiler don't care.

I'm really struggling with the "testing private methods is a smell" school of thought. Modules, classes, methods-- these all are essentially means of decomposing a code base into smaller parts. Why should it be ok to test some of them in isolation, but not others?

@scotthannen Just don't call it abstractions, because that's the language of the ivory tower

Do people who say they hate abstractions put all their code in one big method? Why not?

Just wow.

@rewedigital @DrOetkerPizzaDE Die Ofenfrische Pizza Salami Jalapeño ist online nicht vorhanden. Vielleicht ein encoding problem wegen dem ñ? Ansonsten ist die App echt gut 👍

@rakyll The book DRiVE explains this goodreads.com/book/show/6452…

employed: 8am-5pm: feels drained and never want to touch a computer again unemployed: 6am-10pm: feeling energetic enough to work for another 12 hours if days were longer

@jasongorman If customers are satisfied enough with blue squares, yes.

@kelseyhightower Why would you decide to invest into HA for front desk printers rather than online solutions? I'm not into compliance but my gut feeling is pointing in that direction 👉🏼⚖️

Memo to my younger self: Read this -before- starting my first job 😌📖

@chronark This happens when you have no idea how you want to use the data but you also don't want to delete it. Save it cheap.

Lots of people suggest or offer storing logs and stuff in s3 but can I actually query that without loading everything in memory first? Or is it just a cheap way to archive data?

@bryanl Why do you think that redundancy a problem in human interaction?

What’s worse? Replying to a slack message of “Hello” with “Hello” or “nohello.com”? The former may seem redundant or a waste of time, but the latter is passive aggressive at best and comes off rude.

@rickasaurus As this kind of work has less rules and processes, more experienced engineers are needed.

Why does it seem like older programmers almost always end up in DevOps or infra?

Wow, this is just so enjoyable listening to someone who really knows what they're talking about. youtube.com/watch?v=sr0ar5…

@unclebobmartin @MisterEGC How can you be part of a scrum team that should deliver asap when you have only 1 hour coding per day? For implementation tasks that have 2nd priority, I understand that they have time but for stream aligned teams not. 🤔

I faced this dilemma back in the late’80s. I’d been a developer for 18 years but accepted a position managing development in our UK office. This was a great opportunity for me and my family. I solved the coding dilemma by adjusting my hours. I got to work an hour before anyone else and wrote code. I put the day’s schedule on my whiteboard in 30 minute blocks. That schedule usually filled up within the first hour after everyone arrived for work; but any block left unreserved was coding time. I usually left work an hour earlier than most. This worked, more or less, but it was always a challenge.

29 years as a professional software dev and I’ve always been adamant about staying a dev. But… I just caved in and accepted a “promotion” to dev manager, with the assurance that I would still get to code, (don’t laugh.) Gotta admit, I have mixed feelings about it. #iosdev

@StephenPHassall Maybe you didn't notice but SQL evolved a lot in the last 20 years. XML JSON Composite types Arrays Hierarchical and recursive queries Window Functions MERGE Temporal Databases Multidimensional Arrays Graph Queries What did I forget? ...and it's backwards compatible 🎉

SQL is a nice place to work in. It doesn't change. It's older than me. It's simple to learn, no OOP, no async promises, etc. There aren't people creating new frameworks every week for it. What you write today will work in 10 years time.

@unclebobmartin What did these persons do that you blocked them?

It turns out that the more assholes you block the more reasonable everyone on X becomes. Whodathot?

@unclebobmartin When is the correct time to refactor an if/else into polymorphic classes? It takes some effort. 😶

The problem with switch statements and if/else chains is that they replicate like gerbils. If you aren't careful to sequester them in the early stages of your project, you'll find them reproducing in every corner of your application.

@allenholub Just for fun maybe? "Sprint SpongeBob 🧽" 😂

I hear a lot of discussion about how to name Sprints, but my question is: _why_ would you name a Sprint? The practice has always baffled me. What exactly do you do with that name?

Feeling highly productive by releasing a blog article on my first working day in 2024 😎 Our AWS SQS Metrics - ConSol Blog blog.consol.de/it-consulting-…