Yeah, letting someone work in isolation for three months sounds insane to me.
|
|
# ¿ May 27, 2016 23:20 |
|
|
# ¿ May 31, 2024 12:21 |
Gounads posted:Saturday morning on a long weekend: Oh hey, no worries - I'll push the deploy button then go frolic in the sun. We make sure never to push anything new on Friday, even.
|
|
# ¿ Jul 2, 2016 22:45 |
sarehu posted:Huh? You don't have 7 days of vacation to schedule? You shouldn't have to burn vacation for surgery recovery. That's literally what short-term disability is for.
|
|
# ¿ Jan 26, 2017 23:43 |
sarehu posted:If you paid for short-term disability insurance. But if you haven't, then you should have to burn vacation. I guess I've been spoiled by a startup and then a European company, but this sounds insane.
|
|
# ¿ Jan 27, 2017 03:51 |
My company just got bought by Nokia, and their policy is 22 vacation days on top of about 5 national holidays. Sick leave isn't limited, but after about 5 days sick, they want people to do short-term disability.
|
|
# ¿ Jan 27, 2017 16:51 |
ChickenWing posted:Oh, the joys of neo-socialism () and the banking industry So my old gig had unlimited vacation, which sort of meant you felt bad about taking vacation days. I took less vacation under that policy than with my current 22-day policy.
|
|
# ¿ Jan 27, 2017 20:26 |
Plorkyeran posted:I make changes that cause tests which were originally added to repro a bug to fail all the time. It's really nice having a test suite that's extensive enough that it can be used to test hypotheses about changes, and adding tests as you encounter bugs is a decent way to incrementally get there without specifically dedicating time to expanding your tests. Amen to this. Sometimes a change in behavior is necessary, and a git grep isn't enough to make sure everything lines up properly. Getting rid of unit tests should be reserved for getting rid of functions.
|
|
# ¿ Apr 10, 2017 06:37 |
Yeah, the only times I've had to force anything, I'd hosed something up badly.
|
|
# ¿ Apr 15, 2017 17:39 |
Yeah, I push to the remote version of my own branch, then make a PR. The above sounds like a nightmare. This thread is making me terrified about how devs understand git. a foolish pianist fucked around with this message at 04:01 on Apr 17, 2017 |
|
# ¿ Apr 17, 2017 03:55 |
Pollyanna posted:Is it considered normal/kosher to push in changes for an unrelated ticket to your PRs? My coworker was just s out to approve another coworkers PR but he suddenly pushed changes that we didn't expect, and I suggest occasions like that, where stuff goes under the radar, is a cause of unforeseen and difficult to trace bugs and regressions in our project. I hate when PRs have unrelated stuff in them. PRs are for specific features or fixes. Occasionally, a tiny fix can go in something unrelated, but if it's more than a line or two (with a commit message like "found this tiny error in process, fixed while testing" or somesuch), it needs its own PR.
|
|
# ¿ Apr 25, 2017 16:38 |
Pollyanna posted:That other coworker just declined a pull request for a basic copy change due to a bug in a completely unrelated part of the code base. Is it wrong of me to be pissed off over this? It's not even my PR but it's ridiculous for a really simple, basic PR to be rejected because there's a bug in a totally different part of the codebase. Wait, so he declined because there wasn't unrelated stuff in the PR?
|
|
# ¿ Apr 25, 2017 17:23 |
Yeah, if the guy wants something unrelated to get fixed, make a ticket, fix the thing in its own fix-branch, make a PR, done.
|
|
# ¿ Apr 25, 2017 18:34 |
HardDiskD posted:No, work can still happen in other branches, but I wouldn't merge any until the parent is fixed. Yeah, it is a huge blocker, but something has already failed if a commit/branch with bugs already went into a dev/master branch. This sounds insane. If there's something else broken on master, make a separate ticket and fix separately. Unless you're in a shop where there's only ever 1 bug at a time, in which case get me a job there.
|
|
# ¿ Apr 25, 2017 19:01 |
KoRMaK posted:The ritual is that you gotta recite it at the beginning of every sprint, after tickets have been estimated. That last sentence can really change the meaning, depending on how you read it.
|
|
# ¿ May 5, 2017 20:53 |
Yeah, squashing them is good practice. At my shop, we review unsquashed PRs, but squash them before merging. Keeps the history cleaner, but allows more detailed review.
|
|
# ¿ May 8, 2017 14:21 |
Gounads posted:Bitbucket has an open to auto-squash on merge. Full commit history during code review and readable commit history on master. Yeah, github has this as well. It's super handy.
|
|
# ¿ May 8, 2017 15:31 |
Pollyanna posted:You don't have to comment as you step through, I just wait until the end before I bring up stuff that didn't eventually get addressed. Granted, I do this mostly for large scale changes instead of relatively minor things, so maybe it's different in that case. For bug fixes, it's easiest just to look at the final diff. For larger features, though, the commit history shows a lot about the design process, and it can be handy to look at it.
|
|
# ¿ May 8, 2017 16:37 |
Google is all about precision, rather than recall, in their hiring. They miss a lot of good candidates because of the process, but it works well.
|
|
# ¿ Jun 4, 2017 23:16 |
Yeah, likewise.
|
|
# ¿ Jun 9, 2017 23:40 |
Clanpot Shake posted:Half way through my initial phone screen with Amazon I realized I really, really didn't want to work there. Only twice has a recruiter call set off alarm bells in my head and that was one of them. What made you feel that way?
|
|
# ¿ Jun 12, 2017 23:05 |
Pollyanna posted:Vim and emacs are genuinely powerful, from what I've used of them, but they've also got a hell of a difficulty curve. IDEs are easier to use, but restrictive, and they expect you to work on a set of rails. Text editors like Sublime and Atom are a nice medium between the two. Our whole shop is either sublime or vim (and one weirdo who uses emacs). People trade vimrc lines and give occasional usage tech-talks. I personally wouldn't survive without ctrl-p. I never have to remember where anything is.
|
|
# ¿ Jun 20, 2017 16:28 |
I love Prolog so much. Did a bunch of my masters NLP work with it. It's such a shame no one in industry uses it or even cares that it exists.
|
|
# ¿ Jun 23, 2017 19:17 |
I just got this:quote:Hope you are having a great day ! from an amazon recruiter. Note that I don't work for Amazon, and apparently they're not interested in hiring me (I asked, based on this message). This seems unethical, basically cold-calling people to act as recruiters for them, with no incentive. I haven't seen this kind of thing before.
|
|
# ¿ Jul 5, 2017 17:45 |
They will leave him trapped in the room.
|
|
# ¿ Jul 5, 2017 18:18 |
Yeah, seems like a simple question to get you to talk through some different strategies for repeating processes, recursion vs. iteration. Or just a way to avoid bothering with a 4-hour interview for someone who can't think of an algorithm to reverse a loving list, jesus.
|
|
# ¿ Jul 18, 2017 23:11 |
lifg posted:This time of year is very slow for some industries. Lots of executives take vacations in August. Yeah, seriously. We do a lot of business with European ISPs, and everything just shuts down for the whole month of August. From an American standpoint, it seems insane. Wish I could take the month off too, though.
|
|
# ¿ Jul 29, 2017 04:06 |
Volguus posted:To be honest, when I arrived in Canada and heard that the minimum required vacation days per year was 10 (while most employers were offering 15) I thought that was loving insane. How can anyone live with less than 25 working days per year of vacation, like normal people get? Then I heard about US. I get 5 weeks paid vacation, but I suspect that's because Nokia, which just bought us, is a Finnish company. Prior to that, we were on the typical startup unlimited vacation plan where you actually are working on things and need to finish them and so don't take very much time off. We don't just all leave at the same time, though.
|
|
# ¿ Jul 29, 2017 14:59 |
Rubellavator posted:It's all work for one release that began last year. We don't merge to master until it's released. When work for a release is done we make a branch off of dev for the release. The release branch is tested and any bugs are fixed on that branch. When the release branch is done and passes all testing it's merged to master and dev. So master has just been sitting untouched that entire time? What even is its function, then?
|
|
# ¿ Aug 10, 2017 04:23 |
meatbag posted:I had a postmortem after a job interview for a job I didnt get, and the HR rep said explicitly that my lack of early return statements was a deal breaker. Wait seriously? You were turned away because of stylesheet issues? Sounds like a bullet dodged rather than a job missed.
|
|
# ¿ Aug 19, 2017 12:06 |
necrobobsledder posted:The place is a complete and utter clusterfuck and our SLAs would probably be met better by developers' laptops than our actual servers that we can't afford anyway. This is horrifying. "Sorry, customerdude, we dropped your production server at the bus stop. Expect a few days of downtime."
|
|
# ¿ Sep 7, 2017 16:04 |
Do you have a coworking space near you? Here in Ann Arbor, there's a decent space available for about 40 bucks a month. Well worth it for remote people who need office-like space.
|
|
# ¿ Oct 26, 2017 17:27 |
New Yorp New Yorp posted:Developers have access to production systems and production systems contain PII? What industry are you working in? This is really common.
|
|
# ¿ Nov 7, 2017 22:29 |
lifg posted:I spent so long in college learning about time v space trade-offs in programming, but software development is all about development speed v correctness of new features. This little fact is something that didn’t really sink in until just recently when I read the Google SRE book. I work with high-throughput data pipelines, and both time and space complexity are real issues for our company. We spend a lot of time trying to make sure our processes work as quickly as possible. Until I got this job, I never really had to fret about about optimizing code, but now I'm really glad of those algorithms courses.
|
|
# ¿ Dec 6, 2017 18:50 |
Pollyanna posted:At what point during a struggle in replicating a bug/feature state where wrangling the data itself is unavailable to you and following the steps to do it via the program itself doesn’t work locally is it better to just push a change you are pretty sure will fix the problem and hope it works? Cause I’m really losing patience here. Does this make me a bad engineer, or just a mad engineer? Do you have any environment (staging, some prod deployment no one cares about, anything) where you can pull your changes to and test? Or a prod environment you can push your code up to and run manually without installing and loving up the prod system's normal functions?
|
|
# ¿ Dec 6, 2017 22:19 |
Pollyanna posted:Ended up camping more rooms and doing the latter. Heard a lot of "who the gently caress are you"s but hey, I got my ticket done vv That's pretty much how I live my life. Test code by running poo poo manually on production deployments.
|
|
# ¿ Dec 6, 2017 23:05 |
Skandranon posted:Why can't you make sub branches of your feature branch? Yeah, seriously. Just call that feature branch a a feature integration branch or something, have everyone create branches off of that, merge their branches into the integration branch, merge the integration branch into whatever branch it diverged from.
|
|
# ¿ Dec 11, 2017 23:43 |
Sedro posted:Many people don't realize you can open Github PRs to any branch, including other open PRs. You can change the base branch any time. I think this is the crucial thing. People don't understand how branching works, or how flexible branches are.
|
|
# ¿ Dec 12, 2017 03:50 |
Well-connected kids at good schools can sometimes get insane amounts of money just thrown at them for impossible projects, cf Elizabeth Holmes and Theranos.
|
|
# ¿ Jul 17, 2018 20:46 |
Janitor Prime posted:Every tech sector in every country is doing this poo poo. When I interviewed at a Munich startup it was for a Ninja Devops position :/ What do they mean by ninja devops?
|
|
# ¿ Jul 18, 2018 18:28 |
|
|
# ¿ May 31, 2024 12:21 |
When Nokia bought my company, we went from a startup-style unlimited vacation policy to having 22 use-them-or-lose-them (my state allows this instead of days rolling over or getting paid out - thanks, Michigan) vacation days plus public holidays, and I've taken twice as much vacation under the new system. If I stick around 2 more years, that'll jump to 27 days. Working for a Finnish company hath its benefits.
|
|
# ¿ Aug 13, 2018 14:43 |