this post was submitted on 15 May 2024
88 points (96.8% liked)

Programming

17432 readers
272 users here now

Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!

Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.

Hope you enjoy the instance!

Rules

Rules

  • Follow the programming.dev instance rules
  • Keep content related to programming in some way
  • If you're posting long videos try to add in some form of tldr for those who don't want to watch videos

Wormhole

Follow the wormhole through a path of communities !webdev@programming.dev



founded 1 year ago
MODERATORS
 

I've heard it thrown around in professional circles and how everybody's doing it wrong, so.. who actually does use it?

For smaller teams

"scaled" trunk based development

you are viewing a single comment's thread
view the rest of the comments
[–] KindaABigDyl@programming.dev 9 points 6 months ago* (last edited 6 months ago) (7 children)

Yes. We use SVN. I hate it. I'm trying to build a case to switch to git. We're a small team, but a growing team

[–] CrypticCoffee@lemmy.ml 4 points 6 months ago* (last edited 6 months ago) (5 children)

Do you really need to make a case? Does your company not trust devs? Is there people leading that have no idea about technology? SVN is dead. Many devs won't touch it. It's best way to say to new candidates your company is backwards. Many would refuse to work in a company that uses a version control system that has been dead 7 years.

[–] KindaABigDyl@programming.dev 3 points 6 months ago (1 children)

It's effort to switch, and we don't benefit from having separate copies of the repo bc we're so small. No one steps on eachother's toes, so distributed version control isn't necessary.

Now, the fact that most devs know git and SVN is dead is not lost on our CTO, but putting the effort to switch over doesn't provide direct value to the customer, so I have to make the case that switching to git would do enough from a productivity and maintenance standard to effect customers.

[–] shasta@lemm.ee 0 points 6 months ago (1 children)

But just productivity and maintenance but if your devs start to leave or retire, you're not gonna get the best quality replacements for them if you're using outdated tech. No one wants to learn new skills that aren't going to help with their career growth.

[–] KindaABigDyl@programming.dev 1 points 6 months ago

I'm a relatively new hire and we just hired another person 2 weeks ago

load more comments (3 replies)
load more comments (4 replies)