AtNightWeCode

49 ms·

1. 1111.▲
   by AtNightWeCode 5y ago

   Apologies to the Encore team. A bad comment. /A bitter coder
2. 1112.▲
   by AtNightWeCode 5y ago

   Platforms are typically garbage. This is garbage. Love this quote by the way. "With Encore you write your apps using Go, a modern programming language developed by Google to make backend development simpler. Rapidly growing and designe
3. 1113.▲
   by AtNightWeCode 5y ago

   I have been perfectly happy with ES cloud services. Is this done by honest intentions from AWS or is it simply based on the fact that ES are making a lot of money of the cloud services?
4. 1114.▲
   by AtNightWeCode 5y ago

   Well, no, the main issue usually is that people are not using percentiles. Yes, you can find rare cases by doing this. But you will get false positives I guess.
5. 1115.▲
   by AtNightWeCode 5y ago

   I think time will tell that ANY cluster setup is a high risk for smaller businesses. The amount of knowledge needed to run it in production is much higher than to set it up. I have setup Kubernetes but never run it myself in production. But
6. 1116.▲
   by AtNightWeCode 5y ago

   Writing a topic about programming without mention the term TEAM. Of course programming is hard for you.
7. 1117.▲
   by AtNightWeCode 6y ago

   Best practices are for beginners. Experts don't think about rules.
8. 1118.▲
   by AtNightWeCode 6y ago

   One problem for me in Software development have been bosses, project managers, product owners, IT architects and so on. Sometimes they get too much power and are allowed to make decisions on how to write software. Bad code can be handled. H
9. 1119.▲
   by AtNightWeCode 6y ago

   I think one of the major advantages of writing testable code is that you get better code and architecture for free. You end up with less stateful code, more pure functions, more clear dependencies, fewer hard coded things, flows that are un
10. 1120.▲
    by AtNightWeCode 6y ago

    To expect manual or automatic tests to cover all changes is naive. If people start to make changes that is not related to the actually task. The risk of missing something is kinda obvious. You (and the op) is barking up the wrong tree. Sure
11. 1121.▲
    by AtNightWeCode 6y ago

    I guess I could tell you but I also guess you will not understand. Have you ever had a bug in production on a site that can sell for 10 000 000€ on an evening just cause some guy corrected a stupid spelling mistake? I have. What I'm sa
12. 1122.▲
    by AtNightWeCode 6y ago

    So, in Agile development it is important to do things in priority order. A typo should practically NEVER be fixed if it is not in the comments. So, this is not a GIT issue. This is doing the wrong thing at the wrong time! And, I really, rea
13. 1123.▲
    by AtNightWeCode 6y ago

    One purpose for a low TTL in the solutions I have built is that you want to change the IP. So first you hit the DNS. You get an IP from some main location. Then after the first request you figure out where the user is located. Perhaps spins