|
Protocol7 posted:I'm probably a dumbass, but what does SE2 and SE1 stand for? Presumably Software Engineer 1 and Software Engineer 2. Those are usually positions for fresh college graduates and someone with 2-3 years of experience respectively.
|
#
?
Sep 16, 2020 16:56
|
|
|
|
| # ? May 11, 2024 06:30 |
|
|
csammis posted:At my last job that person was the CEO of the company When our new (remote) CTO started he wanted to fire some senior people because they weren't performing by the metrics of 'lines of code changed' and 'pull requests opened'. I told my wife this and she said "I just work in medical admin* and I know lines of code is a bad metric"  * she's actually full-time unofficial IT helpdesk for a bunch of boomers counting days until retirement and part-time admin, from what I hear
|
|
#
?
Sep 16, 2020 17:20
|
|
|
Protocol7 posted:I'm probably a dumbass, but what does SE2 and SE1 stand for? Software Engineer 1 and 2. In a lot of companies, dev jobs have a ranking that looks more or less like: - Junior, Associate, etc: fresh out of college/bootcamp and still learning, half a step above an intern - SE1: a year or two of experience, junior dev - SE2: plain old journeyman developer, starts at 3-5 years for most folks and can go for the rest of their career - Senior SE: this is the first promotion that's not basically automatic with time in the job at most places. Still an individual contributor, but taking on more architecture and planning responsibility compared to a line dev. Rough rank equivalent to a junior manager - Staff/principal SE: very senior expert who's probably spending more time in architecture and planning meetings than heads down coding. Rough rank equivalent to a senior manager or director - Technical fellow: galaxy brain architect that gets called in for big strategic architecture or as support on really thorny and expensive problems, probably only a handful of these folks even in a large company. Rough rank equivalent to a VP, might report directly to a C-level
|
|
#
?
Sep 16, 2020 18:08
|
|
|
Munkeymon posted:When our new (remote) CTO started he wanted to fire some senior people because they weren't performing by the metrics of 'lines of code changed' and 'pull requests opened'. I told my wife this and she said "I just work in medical admin* and I know lines of code is a bad metric" Well doctors get paid based on how many tests they run, why should developers be any different?  On another note, how should I bring up concerns with the dev team getting overloaded? In the past few months, the following duties have been added (in addition to the standard development stuff):
It's getting to be a little much.
|
|
#
?
Sep 16, 2020 18:15
|
|
|
Our company obfuscated the junior/mid/senior levels with position names that are impossible to discern experience from. I never have any idea how much experience to assume someone from another part of the company has.
|
|
#
?
Sep 16, 2020 18:57
|
|
|
Pedestrian Xing posted:Well doctors get paid based on how many tests they run, why should developers be any different? If you've got the team on your side (or maybe only loop in the lead) can you just measure it for a week or two? Rough hours of each of those for the team then take it to whomever and say 35% of time is on these new responsibilities which means what would be a two month new work estimate will now be three months. Probably worse with context switching and prod emergency situations.
|
|
#
?
Sep 16, 2020 20:04
|
|
|
Pedestrian Xing posted:Well doctors get paid based on how many tests they run, why should developers be any different? Isn't this what they mean by "full stack devops"
|
|
#
?
Sep 16, 2020 20:07
|
|
|
Its like a horrible cargo-culting of SWE oncall.
|
|
#
?
Sep 16, 2020 20:26
|
|
|
Volmarias posted:Isn't this what they mean by "full stack devops" full slog devops. Nobody (at least not immediate management) super seems to care about site stability or whether our fancy browser testing detectably reduces defects. Mostly I feel like I have incentives to go through the motions on some stuff engineering leadership cares about but at review time they want business metrics for new product to be good. Yeah, I go on rotation and watch as dependencies I don’t control fall over. I write whatever browser automation tests QA dictates to me to be written in whatever framework we’re using this week. Otherwise I’m incentivized to ignore it and try to make business number better with new feature as demonstrated by cherry picked A/B test stats.
|
|
#
?
Sep 16, 2020 20:33
|
|
|
Also late to the PM chat but my experience with a few good PMs has been that they've been able to bring the team along on why something is being built. For example "We're building this new onboarding flow because we know if customers integrate with this feature they are twice as likely to renew their contracts, and currently only 30% of new customers enable this". That will also let you use the knowledge and creativity of the team to achieve that goal rather than them just plugging away at "As a customer, when I click Get Started button I will begin the integration wizard so that I can integrate". Step one is obviously having leadership support for your teams working at goals like that and not feature checklists from sales, step two is getting good at data and experimentation to be able to decide what the most impactful thing to build is for any given goal. @johncutlefish on twitter is good in this space.
|
|
#
?
Sep 16, 2020 20:34
|
|
|
Pedestrian Xing posted:Well doctors get paid based on how many tests they run, why should developers be any different? Bring them up and then ensure that you are prioritizing those over stories. "Velocity has dropped by 60% corresponding to increased completeness in the definition of done and prioritizing non-sprint work over sprint work."
|
|
#
?
Sep 16, 2020 21:37
|
|
|
Destroyenator posted:Also late to the PM chat but my experience with a few good PMs has been that they've been able to bring the team along on why something is being built. This is huge for me. I like working on stuff that feels like it creates value for people. If something seems dumb or useless I'll drag my feet hard on it.
|
|
#
?
Sep 17, 2020 05:15
|
|
|
https://twitter.com/isislovecruft/status/1292331568330022913
|
|
#
?
Sep 17, 2020 18:02
|
|
|
If we weren't remote, I'd prefer post-it notes, too
|
|
#
?
Sep 18, 2020 05:23
|
|
|
We’re migrating from a self hosted gitlab to azure devops and I’m really dreading this move. As far as I can tell you can’t group related repositories together and you don’t really have a per repository issue tracking unless I’m missing something so I feel like its all going to be a huge mess. I just wish we would move to github instead.
|
|
#
?
Sep 18, 2020 22:44
|
|
|
Munkeymon posted:If we weren't remote, I'd prefer post-it notes, too Post-it notes with a webcam pointed at the wall and a robot to move them.
|
|
#
?
Sep 19, 2020 00:16
|
|
|
Plorkyeran posted:Post-it notes with a webcam pointed at the wall and a robot to move them. Real talk I tried to rig this up with a lego mind storm set many years back.
|
|
#
?
Sep 19, 2020 00:19
|
|
|
Living the Dream:quote:Sorry I missed your comment of many months ago. I no longer build software; I now make furniture out of wood. The hours are long, the pay sucks, and there's always the opportunity to remove my finger with a table saw, but nobody asks me if I can add an RSS feed to a DBMS, so there's that :-)
|
|
#
?
Sep 22, 2020 08:58
|
|
|
netcat posted:We’re migrating from a self hosted gitlab to azure devops and I’m really dreading this move. As far as I can tell you can’t group related repositories together and you don’t really have a per repository issue tracking unless I’m missing something so I feel like its all going to be a huge mess. I just wish we would move to github instead. Honestly at this point just move to GitHub -- that's the direction that Microsoft is pushing, and I'm pretty sure they're scaling down investment on the Azure DevOps platform.
|
|
#
?
Sep 22, 2020 15:09
|
|
|
New Yorp New Yorp posted:Honestly at this point just move to GitHub -- that's the direction that Microsoft is pushing, and I'm pretty sure they're scaling down investment on the Azure DevOps platform. I'm not sure where you're seeing this, but... no. MS is putting a huge amount of time, money, and energy into developing and selling ADO. Their product strategy split is emblematic of the two opposed groups that hold a lot of power in the company: the new-school folks who want to be startuppy, build exciting new software, open source it, and make money selling services and mandatory ads baked into everything are the ones backing Github. The old-school folks who want to build boring enterprise software, send people in suits to sell licensing deals at staggering costs, and keep everything under tight MS control are backing ADO. Neither one is going away without somebody winning that fight, and senior leadership doesn't want either one of those groups to go away. As far as the mechanics of ADO go, the actual repo part is a tiny piece, and the real functionality is in the project planning and CI/CD tools. Repo hosting in ADO is pretty simple because it's just Git, with a few bits on top that hook nicely into those project planning and CI/CD pieces so you can enforce things like "PRs must be tied to stories." In general, ADO wants to group everything as "projects." Want to make a group of a few repos? Throw them in the same project, where they'll be associated with the project planning and build/release orchestration components of that project as well. If you want to link an issue to code, it wants to put issues against specific commits, branches, or build artifacts rather than repos. Like a lot of Microsoft's in-house-developed, enterprise-focused products, ADO is very opinionated about how you should be doing things. If you learn the flow they expect you to use and adapt to it, it works pretty well. If you try to clobber it into working like another tool, you're in for a world of pain and manual secondary systems.
|
|
#
?
Sep 22, 2020 15:39
|
|
|
Space Gopher posted:I'm not sure where you're seeing this, but... no. I'm very familiar with Azure DevOps. I'd say it's overall, end to end, a superior platform in most regards at the moment. However, the name Github has a lot of sway in the industry and it's not in Microsoft's best interest to actively develop parallel, analogous features for two platforms that serve the same purpose. See: Github actions and Azure pipelines. A lot of the underlying code is shared between them but their ultimate implementations are wildly different and represent a ton of duplicated effort. Thus, the internal emphasis is likely on feature parity for the two platforms, then gradually sunsetting Azure DevOps over the next 5-10 years. In the short to medium term, I'd expect to see public recommendations to use Github for everything except for the areas where Github has no equivalent (manual testing tools) or weak equivalents (project planning tools).
|
|
#
?
Sep 23, 2020 04:52
|
|
|
I don't really have a choice in the matter tbh. If I did we would stick with gitlab, but the company that acquired us some time ago is all in on Microsoft products so that's what we're going with. We have a ton of repos and services and stuff and gitlab worked very well for this since things could be grouped together in sane ways. I know you can have multiple projects in Azure Devops too but that doesn't really work with the project planning stuff as far as I can tell. Like we don't have teams that work on one project and only that project any given sprint, for example. I'm not really sure github would be much better but then you can at least have per-repo issue tracking. The azure devops way seems a bit backwards to me.
|
|
#
?
Sep 23, 2020 16:26
|
|
|
netcat posted:I don't really have a choice in the matter tbh. If I did we would stick with gitlab, but the company that acquired us some time ago is all in on Microsoft products so that's what we're going with. We have a ton of repos and services and stuff and gitlab worked very well for this since things could be grouped together in sane ways. I know you can have multiple projects in Azure Devops too but that doesn't really work with the project planning stuff as far as I can tell. Like we don't have teams that work on one project and only that project any given sprint, for example. GitHub is a Microsoft product. Putting that aside, you have to keep in mind that Azure DevOps was originally created in 2005 and has massively evolved over time. However, a lot of the top-level idioms are rooted in 2005 ways of thinking about things. They've broken down a lot of the walls between projects (which were originally intended to be totally isolated from one another). There used to be thinking that you should have a single project, using the concept of Teams within a project to isolate permissions and work item management (work item permissions can be set at the Area level, and each team is provided a unique top-level Area that they can then subdivide as they please). You can then create higher-level teams to view work and boards across all the "sub-teams". However, there is no way to subdivide or group repos within a team project.
|
|
#
?
Sep 23, 2020 17:12
|
|
|
New Yorp New Yorp posted:GitHub is a Microsoft product. Yeah I know GitHub is Microsoft, but apparently it's still not an option. Well, I'm sure ADO is fine, the project management tools are certainly better than in gitlab for example. Not sure if it's a good fit for us though but I'll guess we'll see.
|
|
#
?
Sep 23, 2020 18:23
|
|
|
I keep seeing requirements that are crying out for elixir/erlang paradigms, but I know nobody else will agree to use it 
|
|
#
?
Sep 24, 2020 10:44
|
|
|
What sort of requirements does it do well? I'd love to add another tool to my kit if it's really that distinct
|
|
#
?
Sep 24, 2020 12:07
|
|
|
Has anybody else looked into OCR applications to turn screenshots of text into actual text? I think I'm done pissing in the wind when I get those and just want something I can quickly search through.
|
|
#
?
Oct 2, 2020 17:54
|
|
|
AWS Rekognition can do that I'm pretty sure.
|
|
#
?
Oct 2, 2020 18:16
|
|
|
At my work we use Abbyy FineReader and whatever Nuance’s solution is called
|
|
#
?
Oct 2, 2020 18:35
|
|
|
Hmm now I have to reconcile that with the image being technically company-confidential. I guess the typical thing is to convert to PDF so it makes me wonder if we have a license to something already. That's probably me best bet.
|
|
#
?
Oct 2, 2020 18:50
|
|
|
Apparently Hacktoberfest has just started and I'm thinking of joining to get some practice in. However the tagged issues seem to be widely inconsistent in scope and quality. For those of you participating, how do you pick what you're going to work on?
|
|
#
?
Oct 2, 2020 21:41
|
|
|
scissorman posted:Apparently Hacktoberfest has just started and I'm thinking of joining to get some practice in. The trolls have kinda killed it this year.
|
|
#
?
Oct 2, 2020 21:43
|
|
|
Yeah, apparently some YouTuber showed people how to make PRs and his examples were extremely low quality, so a whole bunch of people went out and made a bunch of garbage PRs right from the start. Sort of killed the mood for this year's Hacktoberfest. Me, I might see if some of the npm packages I use have easy to address issues, otherwise, guess I'm not getting a free shirt. 
|
|
#
?
Oct 2, 2020 22:04
|
|
|
I like issues that are either bug fixes that I've encountered in the wild or are at least in libraries I use. It's instructive to actually set up a project you use and try to implement a minimal change. Failing that I'd probably just work on a personal project since contributing to your own open source project is in no way cheating.
|
|
#
?
Oct 2, 2020 22:15
|
|
|
I'll take another look tomorrow, right now there are too many issues with either "do this trivial task" or "implement a ui".
|
|
#
?
Oct 2, 2020 22:24
|
|
|
Well instead of pushing to master like I usually do on personal projects, I'll make PRs and then go merge them. Easy peasy.
|
|
#
?
Oct 3, 2020 00:11
|
|
|
Protocol7 posted:Yeah, apparently some YouTuber showed people how to make PRs and his examples were extremely low quality, so a whole bunch of people went out and made a bunch of garbage PRs right from the start. Sort of killed the mood for this year's Hacktoberfest. most frustrating of all is that you can do it on your own repos, i think. nothing stopping you from opening a repo and submitting poo poo prs to it
|
|
#
?
Oct 3, 2020 01:17
|
|
|
Except the Hacktoberfest “rules” prohibit that exact thing too:quote:Bad repositories will be excluded. In the past, we've seen many repositories that encourage participants to make simple pull requests – such as adding their name to a file – to quickly gain a pull request toward completing Hacktoberfest. You can even report repositories that exist for the only purpose of gaming Hacktoberfest. I saw that they made Hacktoberfest opt-in by adding a topic to your repo, and they changed the rules so only PRs that are merged count towards your shirt. So I guess that’s a good first step, we’ll see who’s brave enough to put a target on their back I guess.
|
|
#
?
Oct 3, 2020 13:19
|
|
|
Lol all my changes were to my dotfiles repo I really am not much for actual personal projects these days
|
|
#
?
Oct 7, 2020 03:18
|
|
|
|
| # ? May 11, 2024 06:30 |
|
|
I keep a journal in a private Github repo for maximum green squares. It also makes me better at remembering what the hell I'm trying to do at work
|
|
#
?
Oct 7, 2020 14:09
|
|