Conversation

Notices

1. 7666 (7666@comp.lain.la)'s status on Sunday, 11-Feb-2024 12:07:24 JST 7666

   in reply to

   • 受不了包
   • taylor
   • KnottEye
   @shibao @nik @amy industry trends are generally people following gartner magic quadrants as if they were crystal balls. i pay zero attention to them.
   
   your goal is to support the business, not play evangelist. if the industry trend is to go to the cloud, you have to evaluate that against your needs before committing. if more people understood that, the cloud probably wouldn't be the cash cow it is, as the same people calling the cloud a game changer are the same people selling it.
   • † top dog :pedomustdie: likes this.
   • 受不了包 (shibao@misskey.bubbletea.dev)'s status on Sunday, 11-Feb-2024 12:07:25 JST 受不了包

     in reply to

     • taylor
     • KnottEye

     @7666@comp.lain.la @nik@misskey.bubbletea.dev @amy@decept.org eh i'm not sure i agree with that mentality, i like to think of them all like tools, yes maybe you sometimes get totally new tools that are revolutionary and you want to see what it can be used for (in physical tool land, the grabo is one that i'm actually really interested in), but you still have to evaluate every single case and figure out what kind of tool will do the best job
     
     following industry trends just for the sake of following industry trends just means that you don't jump on some of the really bad ideas, but the more you pay attention to industry trends and read up about past trends, the more you'll realize "hey, this is just X from the 90s with a fresh coat of paint" and see through the hype better

   • 7666 (7666@comp.lain.la)'s status on Sunday, 11-Feb-2024 12:07:26 JST 7666

     in reply to

     • 受不了包
     • taylor
     • KnottEye
     @shibao @nik @amy many concepts would be great if people understood how they functioned and did not simply implement them because "new and fancy"
     
     therefore i always recommend staying one generation of technology behind because enough competent engineers will be available to cross examine the shitty ones
     
     therefore, VMs and monolithic service architectures are king. whenever someone does something new and fancy that deprecates microservices, then microservices will be king.
   • 受不了包 (shibao@misskey.bubbletea.dev)'s status on Sunday, 11-Feb-2024 12:07:27 JST 受不了包

     in reply to

     • taylor
     • KnottEye

     @nik @amy@decept.org microservices are literally just an administrative problem that solves the problem of having like thousands of teams at something like twitter build into an application
     anyone who does anything with microservices that isn't at one of said thousands of teams tech company or strictly following something like the actor model is doing definition cargo cult programming lol

   • taylor (nik@misskey.bubbletea.dev)'s status on Sunday, 11-Feb-2024 12:07:28 JST taylor

     in reply to

     • KnottEye

     @amy@decept.org the most solid piece of advice on here

   • KnottEye (amy@decept.org)'s status on Sunday, 11-Feb-2024 12:07:29 JST KnottEye
     I read grugbrain.dev the other day. I want to be like this but I think I am too young and ambitious to really be self-aware smol brain. I am still enthralled by trying to think my to the perfect abstraction before I even start the prototype lmao.
     Sorry to all the self-aware smolbrains and the actual bigbrains cleaning up after me. I am sure that in 10 years I'll be much more pleasant to work with when I stop droning on about type correctness.