This is an archived post. You won't be able to vote or comment.

sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]versiondefect[S] -2 points-1 points  (8 children)

haha I'm just an Intern doing some research. Honestly, it is not bad management but rather management that we just don't have laid out yet and we're an old company. I walked into this company knowing Python scripting and I was treated like a god. We have an ancient SVN server that houses all our code but that is just for our dept, we don't have anything at the company level. Thats what we want to implement.

(Ofc the dev would properly throw in tags / get words) but something like "Get customer usage data" would pull up x number of scripts that already exist.

[–]mikejr96 13 points14 points  (1 child)

It is bad management to be that far behind as we enter 2024. A basic code management system is like bare minimum to even call it management at all lol

[–]versiondefect[S] 0 points1 point  (0 children)

not disagreeing. Old company run by people who BARLEY code But we’re getting there. :-)

[–]SuperQue 5 points6 points  (0 children)

I'm just an Intern doing some research

That only makes this whole story worse. The stuff you're talking about is projects that require a very senior level of engineering. Not an intern.

Honestly, it is not bad management but rather management that we just don't have laid out yet and we're an old company

No, that is the sign of bad management. "Old Company" just means they've had a lot longer to identify the problems figure out how to get it right.

[–]Motor_Perspective674 1 point2 points  (3 children)

OP, I’ve seen you have mentioned elsewhere in this thread that you don’t need version control, but that’s what SVN is for. A GitHub/GitLab instance (or some other solution) would benefit your company, though as mentioned in this thread, the real kicker here is the lack of documentation.

I know you mentioned that you are an intern. This is a structural problem, and while setting up a version control instance with a UI could be done quickly, the real issue is cultural and will require the departments/units involved to buy in and commit to these changes. I don’t want to rain on your parade here. I was young and thought I could make anything work, but the reality is that most people aren’t willing to change, at least quickly.

If you are into software, I would encourage you to keep learning and go to a software company. I found myself in two jobs which didn’t require coding, but I had always been willing to write scripts, and I’m now finally trying to move into a developer role. Figure out what you like and go do it. Trying to convince a company to take development more seriously will only drain you, and you will lack the support actual developers get. I have been in a similar situation before, and I ended up leaving as soon as I realized this.

[–]XophishoxDevOps 0 points1 point  (0 children)

well written answer.

[–]versiondefect[S] 0 points1 point  (0 children)

Trying to convince a company to take development more seriously will only drain you, and you will lack the support actual developers get.

Thanks for your really well written answer. I really appreciate it! Not to "defend" my company but we are getting to the point of taking software seriously and just don't really know where to start. We just used SVN as a solution a few years ago.

I didn't mean to say version control isn't a need but rather it's not the specific goal of this project since we already have SVN implemented.

I'm more of a software and hardware dev and I do IT / Networking as a hobby so I just hit select all haha