Hey wait, where is the trunk? Where are the tags and the branches?
-
I just realised (again) that the svn repository for this project doesn't have a trunk directory, tags, or branches.
It's just bang! There. That's it.
Oh also, the whatever SQL that keeps the index of the repository has been broken for... 3 months now?
I asked the senior dev about it the first day I synchronised with the repository .
Hasn't fixed it yet.
-
INB4 flamewar about Git vs. Mercurial vs. Subversion, including a long blakeyrant about Git and at least 3 people trying to argue with him.
-
Why even bother with branches and tags? Just keep an Excel spreadsheet somewhere that has all the revision IDs.
-
"But we use version control software..."
-
Why even bother with branches and tags?
I don't think my fellow hardware guys and gals even know that branches are a thing.
-
Well yeah, if they are "hardware" people.
-
@HardwareGeek
@HardwareGuy
@HardwareGalTell them to register!
-
The "hardware" is software models of what the hardware is eventually supposed to be. It's stored in version control, just like other software (except the stuff written in the India office; they just email zip files). It's just that everything is done on the trunk.
-
hardware guys and gals even know that branches are a thing.
I got a look from my boss who had got an angry email from Hardware contractor guys, because I dared add lines to the code before first informing them! Apparently I should have sent an email first. Fucking just merge it, merging conflicts is not scary! what is the point of software repository if you cannot use it to collaborate. If you use it like a dropbox to copy crap in it (zip, pdf, excell, cad designs, ...), then make a folder called "archived" to keep more crap like older code just in case .
Forget about issue trackers, that is too hippie for a disruptive technology, send emails. Disruptive my ass, am doing my best to hop this job of less than 2 months and work for someone who understands software.
-
then make a folder called "archived" to keep more crap
Well, it is subversion, so that's just how it does history.
-
It's just bang! There. That's it.
I asked the senior dev about it the first day I synchronised with the repository . Hasn't fixed it yet.
Can't you just do it yourself?
svn mkdir svn+ssh://example.com/trunk for x in `svn ls svn+ssh://example.com`; do if [ "$x" -ne "trunk" ]; then svn mv svn+ssh://example.com svn+ssh://example.com/trunk -m "Creating trunk"; fi; done
or something like that. Probably easier with a GUI of course...
-
Can't you just do it yourself?
@Ascendant's company doesn't pay him to maintain source control.
Actually, they just don't pay him. Period. Full stop.
-
And together they are... the hardware team! They fight crime.
-
@Lorne_Kates said:
Actually, they just don't pay him. Period. Full stop.
technically, if that's the case, isn't he not actually employed?
-
Can't you just do it yourself?
This company, let's say Company-N is not my direct employer. I'm hired by Company-S.
The SVN repository is Company-N's and I'm working on their project.I don't have any say in their data architecture, software design or internal development tools.
-
technically, if that's the case, isn't he not actually employed?
Ah dammit. this comment interface just freaked out and reloaded the whole page. I lost what I was writing.
Anyway, that presents a quite philosophical/existential question.
@Lorne_Kates said:
@Ascendant's company doesn't pay him to maintain source control.
Actually, they just don't pay him. Period. Full stop.
I got paid the rest of the money finally after waiting for some 2 weeks.
Incidentally, payday is very close. Let's see what they do. Would they present more fun stuff for you guys' entertainment?
-
You can keep it in Sharepoint. It has version control
-
@ben_lubar said:
Why even bother with branches and tags?
I don't think my fellow hardware guys and gals even know that branches are a thing.
The SVN repository under the hardware guys' control at my company has branches within tags within the trunk...
-
Who needs branches and tags? Just create a new repository called "trunk-old", and do your work in "trunk". Next time, make "trunk-old-old", then "trunk-really-old", "trunk-older", "trunk-new", "trunk-20150117", "trunk-20150202", "trunk-20152202", "trunk-31115", "trunk-1545", "trunk-1564", "trunk-newfixes" "trunk-reallyfixed", "trunk-fixed", "trunk-broken", "trunk-fragile", "trunk-pretty-hate-machine", and so on.
It should be obvious which one you need, just look at the names.
-
It should be obvious which one you need, just look at the names.
$/trunk/new/company/trunk/truck-final/branch/really-trunk/tags/not-a-tag/trunk
-
@Lorne_Kates said:
Actually, they just don't pay him. Period. Full stop.
technically, if that's the case, isn't he not actually employed?
Oh, he still WORKS for them...
-
@Lorne_Kates said:
Oh, he still WORKS for them...
In search of a new job that sucks less now.
Not so easy since I think I'm in some sort of junior limbo.
Knows enough to see my current seniors are ... , no disrespect but, incompetent at best.
Doesn't know enough to hold down a job abroad that's not a wanted post for a cheap foreign code monkey.Currently I'm just beefing & brushing up on my skills and trying to hold down a job abroad.
-
Knows enough to see my current seniors are ... , no disrespect but, incompetent at best.
But, I'll wager they have a lot more experience dealing with management than you do, and that is why thery're senior...
-
they have a lot more experience dealing with management than you do, and that is why thery're senior...
That would be nice.
But no. Their management skills are "soon" and "maybe".
When is the deadline?
SoonSo what did the users say about the requirements?
You know, nice things, maybe?Although there is a way to get the answers that I want.
Play 20 questions.
Oh wait but I can't play that with the user specification/requirements because when they meet the clients they just have a dinner and just smile all the time.