Cyno

@Cyno@programming.dev

• ⁨Comment⁩ on ⁨Need help understanding how to get around port-forwarding with tailscale⁩ ⁨⁨9⁩ ⁨months⁩ ago⁩:

  I was really hoping there was something like hamachi/xfire/garena from the old days but modernized and more stable 😅 I just assumed it’d be a solved problem by now.

  I’m not giving up on tailscale yet, I’ll try the funnel feature but yeah… seems a bit troublesome for sure

• ⁨Comment⁩ on ⁨Need help understanding how to get around port-forwarding with tailscale⁩ ⁨⁨9⁩ ⁨months⁩ ago⁩:

  Thanks for linking that, seems like a great resource! Seems like there’s a few that support UDP although I’m not sure if they will work with a CGNAT setup, also their setup seems a bit more complicated and technical than expected but I need to look more into it tomorrow. If everyone else needs to have this installed then that might be an issue

• Need help understanding how to get around port-forwarding with tailscale
  Submitted ⁨⁨9⁩ ⁨months⁩ ago⁩ to ⁨selfhosted@lemmy.world⁩ | ⁨14⁩ ⁨comments⁩
• ⁨Comment⁩ on ⁨Reality check: Our Go backend stack⁩ ⁨⁨11⁩ ⁨months⁩ ago⁩:

  I only have half as much experience as you, and none with Go specifically, so I can’t give you any good answers but I can say I empathize - the company I work at is also stuck with a legacy monolith that’s still on .net framework and everything is so coupled that it’s impossible to even unit test, less alone deploy the projects separately. Some people aren’t bothered even with the basic principles of code writing and the senior people are just overworked and can’t keep tabs on it even if they wanted to.

  The worst part is that the company is mostly either juniors just doing what they are told or older seniors that are stuck in their ways and are afraid of anything new - although as I got older I started to see why that might be the correct approach, not everyone wants to learn and adapt to new tech and it’s a big ask of the upper management to risk it on that. Basically we’re just repeating the same mistakes and wasting time fixing known errors that keep happening and any actual improvement or proper removal of tech debt never happens.

  So yeah… I’m starting to believe that “clean good code” only happens either in hobby projects or new startups. Any larger, “stable” codebase of a larger company is going to be an inefficient mess however 🤷‍♂️

• ⁨Comment⁩ on ⁨Why Git is hard⁩ ⁨⁨1⁩ ⁨year⁩ ago⁩:

  I use the CLI for simple commands, especially if helping someone on another PC and I don’t have access to my preferred tool, but I honestly don’t get people who use it religiously and never even try tools with GUIs. The convenience of being able to easily see the commit history, scroll through it, have a right click context menu or ability to just click it and see file changes (and then right click those files for additional options), is just something I can’t abandon. Nowadays even the aliasing can be replicated in those tools if they support creation of custom commands so even that is a moot point - with some setup you can be as fast as with a CLI.