• 0 Posts
  • 44 Comments
Joined 3 years ago
cake
Cake day: June 13th, 2023

help-circle

  • He’s very popular, written several books and spoken at many events. Most notably he’s written Clean Code and the follow up I never bothered reading and he’s a die hard advocate of TDD and also one of the authors of the Agile Manifesto. I met him a few times after his talks.

    I generally “like” Uncle Bob or Robert C Martin insofar as he advocated for better software design and had some good ideas and all that. I personally hate TDD but when you talk to him and stuff, he’s more flexible and nuanced than he can come across. The problem is when he comes up with (or runs into) a new “philosophy” he becomes evangelical about it and it seems like he doesn’t have as much nuance. Sadly though, growing up with his fans in the software industry has been a pain because they’d hear something from him or Fowler or Beck or whoever and then try to reshape the codebase like typical Magpie Developers.



  • Yup. I haven’t touched .NET in forever … like it’s been 7 years or so but I was there for the 1.0 days. I remember running stuff to code gen db tables to objects and NHibernate and Entity Framework and all that jazz.

    I was just like, “wait, why am I writing all of this if it’s just a projection”. Then the Active Record pattern felt limiting when scaling my application. I think after we discovered Dapper… we just stuck with that. It’s a micro-ORM where we write SQL and it maps into C# objects and it just simplified when hydration happens and how. (not sure how much its changed or if it’s even active now, but it was amazing)


  • lobut@lemmy.catoProgrammer Humor@programming.devgotMeThinking
    link
    fedilink
    arrow-up
    3
    arrow-down
    1
    ·
    3 months ago

    I knew some bad devs that didn’t have CS degrees. They joined because they thought the money would be good and the companies wanted to reduce labour costs.

    It’s really hard to explain to someone what loops are that doesn’t get it.

    However some of the “worst” devs that I’ve worked with aren’t incompetent coders. They’re good “coders” that are fucking shit to work with. They refuse to fix their own bugs, blame you for their mistakes, ignore your feedback and management fucking loves them and gives them carte blanche. I’m talking over ten years ago but we implemented some cache system who refused to publish their docs online to “strengthen” relationships with their customers. Anyways, the dude implements it, doesn’t document anything (much like the product itself). Days past after implementation and I see what looks like a cache bug and I say, “Sergii, can we look at this together?” His reply? “No, I’m sick of looking at it” … I go to the manager and he says, “yeah I get what he means, I’d not wanna looks at it either” … great.









  • Yeah, absolutely agreed.

    Btw, you probably already know this, but if you don’t. The later versions of Node can run typescript natively. By “run”, I mean, it can run a subset of the language, if your project indirectly or indirectly references a file that has “decorators” or something like that, then you’ll need to use another compiler.

    ts-node or tsx are runners that I use typically if I just want to “run” something. They’re basically zero config runners and I can debug with them with VS Code.


  • I’m a former .NET dev … I stopped quite a few years ago after I joined a Bay Area company. It was quite a change. React 1 was just coming out and I used to just write bad JS on my webpages and I had to rewrite our front-end in React. Also, ES5 or 6 or whatever was getting popular and we had to transition from CoffeeScript.

    The JS world gave me whiplash after doing so many years of Enterprise .NET. The .NET tools felt so much more polished.

    The fundamentals of Node to me were different than .NET. .NET felt like it had a lot more cruft and “magic” at first. With Node it felt deceptively simpler at first. Then when the require syntax was going away and we had imports but then it wasn’t a real import. It was a TypeScript import or a webpack import that did a require behind the scenes. Then I had to understand why we used typescript but then what was the point of tsc vs babel vs webpack vs esbuild what their roles were and I kind got a bit obsessed with understanding what they did and what was happening under the hood. Then Node officially did do import and I had to understand what that was all about and how it affected our compilers or bundlers.

    Sorry I rant pointlessly. Godspeed on your journey!






  • I will just say that things in tech change a lot in general. That’s just the nature of it.

    If I can do one small thing that makes people feel better, then why wouldn’t I do it?

    I don’t necessarily see that as a connection to a measure of competency. It seems you do and you probably have good reasons to believe so and I would say that I haven’t experienced that.


  • lobut@lemmy.catolinuxmemes@lemmy.worldWhich git branch are you on?
    link
    fedilink
    arrow-up
    23
    arrow-down
    3
    ·
    edit-2
    1 year ago

    If it uses master and it’s too much trouble to get people to switch. It stays master until we can coordinate.

    If I’m starting a new project I use main.

    Why?

    It doesn’t take much to do and it avoids any misunderstandings or arguments and we’ve got work to do. I don’t particular care if you guys are “stuck” on master. If that’s what it is and everyone wants to keep it that way, I don’t have enough will to change it. If it’s under my control, I will change it.