Re:Questions to Ask a Potential Tech Employer
by vonmoltke on Thursday April 14, 2016 @03:34PM
(#11499691)
> q: What do you use for source control? a: We use $NAME but we forbid branching because merging is too hard.
Where I used to work, and the first place I wrote software full-time, we were not allowed to commit code to our system (Synergy) until after our code review. I ended up creating a parallel SVN repository so I could do incremental check-ins.
Don't get me started in merging...
Re:Questions to Ask a Potential Tech Employer
by cableshaft on Friday April 15, 2016 @12:28PM
(#11505552)
I don't think we are supposed to either, but it's never been an issue for our company because there's always shelvesets with TFS, so you can shelve your work at different stages and retrieve it later.
If you're using a DVCS like git, though, that seems silly.
Re:Questions to Ask a Potential Tech Employer
by hackaflocka on Thursday April 14, 2016 @02:13PM
(#11499125)
Sadly, not surprising.
This is the state of most of the industry.
Mostly, only companies with cushy government contracts with unlimited time and expense accounts on their hands (think defense) don't want to fire their customers.
Re:Questions to Ask a Potential Tech Employer
by vonmoltke on Thursday April 14, 2016 @04:04PM
(#11499899)
Unlimited time-and-materials (T&M) contracts are a rare beast. There is almost always a cap that cannot be exceeded without a renegotiation
As for not wanting to fire the customers, upper management may not want to fire them, but those of us actually doing the work sure did. We hoped they would take their so-called "experts" with them.
q: If you could wave a magic wand and change anything about the company, what would it be? a: Get rid of all our customers.
q: How many hours did you work last week? a: All of them.
q: How many meetings were you in in the last few days, and how long did they last? a: Most of what I do is meetings.
q: What do you use for source control? a: We use $NAME but we forbid branching because merging is too hard.
q: Describe your build / deploy process. a: I don't think we have time for that right now.
q: What do you use for a bug / task tracker? a: Email.
q: How would you gague your technical debt? a: What's "technical debt"?