6 ms·
There is no agile, no source control, no meetings If you stop there, it really doesn't sound so bad... Is there a way to present this as an opportunity for re
by matfil 8y ago
There is no agile, no source control, no meetings
If you stop there, it really doesn't sound so bad... Is there a way to present this as an opportunity for reasonably experienced introverts to "own" something without too many interruptions? Or is there enough incidental stuff that it doesn't work like that in practice?
(The "no source control" would probably bug me a bit, but presumably not much stopping someone running their own?)
- hkai 8y agoGood point, I guess this is what I will be writing on my own glassdoor review - there is literally zero office politics and there is every chance to use whatever tool you learn. I personally learned vue.js and secretly transitioned some internal tools to that.
- brokenmachine 8y agoI lol'ed at "secretly transitioned".
- toast0 8y agoThere are a solid group of people who seek out jobs with no agile and no meetings. No source control is a bit out there, I don't want code reviews, but I do want to be able to rely on the source code for what's running on prod to be in the repo within some reasonable time (before it gets to prod is better, but after is ok too, as long as its consistent). Edit to add: > hiring developers because 1) Glassdoor reviews are bad 2) compensation is small 3) work is frustrating 4) you don't learn anything from colleagues Of these, only one is important -- compensation; pay more and people will be willing to put up with a frustrating work environment. Especially if "no meetings" means no meetings. (unlike where i currently work where "no meetings wednesdays" means everybody has room on their schedule on wednesdays, which means that's where the meetings are scheduled)
- matfil 8y agoPrecisely.
- danhorner 8y agoThis is an enlightened and contrarian POV and I'm glad for it.
- pjc50 8y agoNo source control means either no collaboration, frequent merge crises, or hyper-micro-services architecture. Either way it means siloed work and frequent re-work. And no history to help you get on board. (Unless you're following the pre-git Linux flow of having patches merged by the dictator?) If there's no agile and no meetings .. are people just doing their own thing?