|
We use notion at new job, and it seems fine? Like any documentation system, you need people to actually keep it up to date, and while the search doesn't wow me, it lets me edit things easily enough that I can just rewrite docs as I need. My personal preference is for text-based docs in a repo, at least for developer use.
|
#
?
May 24, 2021 10:24
|
|
|
|
| # ? May 9, 2024 14:45 |
|
|
I use Notion for my own note taking. But for team use I’ve heard people talk back and forth about Notion v Roam.
|
|
#
?
May 24, 2021 14:05
|
|
|
Notion is okay, but it just got an API for interacting with it literally this past week.
|
|
#
?
May 25, 2021 03:33
|
|
|
gay_crimes posted:Has anyone used Notion as an alternative to Confluence? Our docs are spread across Confluence, Google docs, GitHub wikis, and more, and we don’t particularly love any of those locations, they all have their faults. Some people on my team and I thought Notion looked nice, and a few have used at other places, but we never pitched adopting it, we joked about how we would be adding to the problem with yet another place
|
|
#
?
May 25, 2021 06:07
|
|
|
the CEO of my company says "frankly" multiple times a day and i've yet to hear him be frank about anything
|
|
#
?
May 25, 2021 06:12
|
|
|
Travv0 posted:the CEO of my company says "frankly" multiple times a day and i've yet to hear him be frank about anything
|
|
#
?
May 25, 2021 06:31
|
|
|
Sagacity posted:does he also say "challenges" instead of "problems"? we don't have those things so neither i guess
|
|
#
?
May 25, 2021 07:21
|
|
|
Travv0 posted:we don't have those things
|
|
#
?
May 25, 2021 08:35
|
|
|
"opportunities for growth"
|
|
#
?
May 25, 2021 10:12
|
|
|
if we think outside the box and open up some bandwidth for us to pivot our product to better navigate these unprecedented times... new normal... circle back... take this offline
|
|
#
?
May 25, 2021 13:31
|
|
|
Sagacity posted:Frankly speaking, if the issue is your documentation is spread out too much then things won't magically solve themselves by adding yet another tool. If nobody is curating any of it, Notion will just end up being yet another dumping ground of docs nobody can find. Yeah, this. Stuff like this is why I'm bummed I didn't get a library degree or some kind of arts degree - as the only in-house software tester, I have a whole bunch of knowledge swirling around my head, a lot of it is not very well explained nor properly documented anywhere (besides inside test plans/bug notes/stories, but those usually don't really explain the full logic, existing limitations, interactions with other parts of the software developed later, nor why I wrote a particular test unless you happen to have a good grasp on how the system works), and I feel like I'm ill-equipped to document and catalogue this info properly. Yet I'm doing it anyway, so I guess someone else can find my half-baked documentation 5 years from now and hopefully has a better chance than I did when I started at this organisation. Speaking of, this past week I discovered a feature that had apparently existed before I arrived at the company, that wasn't set in any environments we had, was never documented anywhere, and the first I heard of it was last week in the form of a passing reference to it while looking for something else in a document written 3 years ago. What makes this even more aggravating is this bit of functionality is very useful and yet apparently nobody knew about it, I assume coz most of the devs have since left. Surprisingly, it still works, hurray.  Edit: Software archaeology is a real thing, yes? 
froglet fucked around with this message at 14:21 on May 25, 2021 |
|
#
?
May 25, 2021 14:15
|
|
|
My transfer from SQA to Junior Dev got approved. Yay
|
|
#
?
May 25, 2021 15:57
|
|
|
RC Cola posted:My transfer from SQA to Junior Dev got approved. Yay Congrats!
|
|
#
?
May 25, 2021 19:14
|
|
|
Got eviscerated on my first feature pr today. Two senior engineers just tag team ripped this thing to shreds in review. I already felt like I took too long to get this feature built in the first place. But at least I was extremely familiar with the code by then. I took it on the chin, worked through three rounds of review for the afternoon, ended up with a far superior pr by the end of the day. I hope their impression of me is the guy quickly fixing things up and not the code I originally pushed, woof.
|
|
#
?
May 26, 2021 02:06
|
|
|
Judge Schnoopy posted:Got eviscerated on my first feature pr today. Two senior engineers just tag team ripped this thing to shreds in review. I already felt like I took too long to get this feature built in the first place. The only time I would think poorly of a junior is if they kept making the same mistakes over and over.
|
|
#
?
May 26, 2021 02:44
|
|
|
Judge Schnoopy posted:Got eviscerated on my first feature pr today. Two senior engineers just tag team ripped this thing to shreds in review. I already felt like I took too long to get this feature built in the first place. They're there to help you grow, by telling you how bad and wrong you are. They won't be upset if you actually grow, it's the opposite, they will be delighted that you can be better.
|
|
#
?
May 26, 2021 03:13
|
|
|
Volmarias posted:They're there to help you grow, by telling you how bad and wrong you are. They won't be upset if you actually grow, it's the opposite, they will be delighted that you can be better.
|
|
#
?
May 26, 2021 12:47
|
|
|
Judge Schnoopy posted:Got eviscerated on my first feature pr today. Two senior engineers just tag team ripped this thing to shreds in review. I already felt like I took too long to get this feature built in the first place. "Ripped to shreds" as in a lot of corrections and comments, or as in "this is bad, you are bad, what tortured mind hath wrought this misbegotten function"? If it's the first - don't take it personally. It feels rough to start, but it's part of the learning process and over time your average comments-per-PR will drop. One of my favourite things about my job is working with Jrs. and watching their overall PR completeness rise over time. We expect a lot of comments and corrections to start, because the more we get worked out now the better course you're on for the rest of the job. If it's the second? 
|
|
#
?
May 26, 2021 14:50
|
|
|
At my company we have some FW that runs on an MCU as part of an IoT device. This FW must support the commercial application, but also R&D functionality and production functionality. Is there any general best practices regarding either maintaining a "single" FW that just supports everything, vs. separate commercial, R&D, and production builds/releases?
|
|
#
?
May 26, 2021 15:27
|
|
|
Judge Schnoopy posted:Got eviscerated on my first feature pr today. Two senior engineers just tag team ripped this thing to shreds in review. I already felt like I took too long to get this feature built in the first place. N-thing what everyone else said. As long as they weren't being assholes about it, this is about helping you improve and maintaining code quality for everyone. Everyone was a junior once, and they're devoting some extra time away from their assigned tasks to help you along the learning curve. Keep at it and you'll be on the other side of these soon enough. Also, and this may just be me, but I actually appreciate when the reviewee ask questions when they don't understand or pushes back a bit when they don't agree with a suggestion. Some juniors are reluctant to do that and just take my word as law. I've been doing this a long time, but I'm not infallible, and having to justify requested changes has helped me catch some of my own mistakes and unquestioned assumptions that I normally would have missed. And even if I'm usually right, it can still be useful to have both sides understand the other's reasoning.
|
|
#
?
May 26, 2021 15:50
|
|
|
Being ripped to shreds is unusual in my non-FAANG experience. Don’t you have a senior developer watching over you to make sure you’ve been on the right track the whole time?
|
|
#
?
May 26, 2021 15:59
|
|
|
chglcu posted:Also, and this may just be me, but I actually appreciate when the reviewee ask questions when they don't understand or pushes back a bit when they don't agree with a suggestion.
|
|
#
?
May 26, 2021 16:05
|
|
|
ChickenWing posted:If it's the first - don't take it personally. It feels rough to start, but it's part of the learning process and over time your average comments-per-PR will drop. This. Nobody is expecting you to write perfect code, especially as a junior dev. Everyone makes mistakes - willingness to work with feedback and improve is what matters. I do try to phrase my comments a little more softly when I'm dealing with someone new though just so they don't take it the wrong way.
|
|
#
?
May 26, 2021 17:55
|
|
|
There is no way a dev team worth their salt is NOT going to shred your first PR. As others have said, as long as it's stuff like, 'This is not the convention we use' and not 'ur bad and you should feel bad', that's a good sign. They want to mold you into a better engineer and I'd personally be really scared if my first PR with a new team doesn't get a lot of feedback. Speaking of which, I start on said new team in 2 weeks. I'm excited and scared. My background is a lot of C# and C++ and I think my first project will be Python, a language I haven't touched in years, so it'll be fun/scary to spin back up on that. I expect my PRs to get shredded.
|
|
#
?
May 26, 2021 23:46
|
|
|
If they were being dicks about it I wouldn't have been cooperative. They were honest and blunt but I definitely felt a vibe of "we're doing this because we see potential". I think the worst comment was "this is interesting", which I read as "lol wtf ru doin," because that's what I thought of when I fixed it.
|
|
#
?
May 27, 2021 01:34
|
|
|
GFD wrong thread
Hughlander fucked around with this message at 02:19 on May 27, 2021 |
|
#
?
May 27, 2021 02:01
|
|
|
Hughlander posted:Boyfriend Won’t wear headphones when I’m home
|
|
#
?
May 27, 2021 02:04
|
|
|
Judge Schnoopy posted:If they were being dicks about it I wouldn't have been cooperative. They were honest and blunt but I definitely felt a vibe of "we're doing this because we see potential". That's a good one, ha. Right alongside "I would not have thought of this" in terms of mystery.
|
|
#
?
May 27, 2021 02:28
|
|
|
Cyril Sneer posted:At my company we have some FW that runs on an MCU as part of an IoT device. This FW must support the commercial application, but also R&D functionality and production functionality. Is there any general best practices regarding either maintaining a "single" FW that just supports everything, vs. separate commercial, R&D, and production builds/releases? Keep them separate you'll have to do insane bullshit in your qc support tests or whatever that you don't want to be in the wild. the r&d stuff is a little more open but probably same. if you really want to you can use cmopiler flags for different build profiles in your CI I guess.
|
|
#
?
May 27, 2021 02:59
|
|
|
To give perspective from another viewpoint, I joined as a senior, replacing the outgoing senior. I tend to work primarily on a green fields project but have to maintain some legacy stuff every now and then. My junior/intermediate has a lot more experience with that stuff so he tends to have useful feedback for me on my PRs, and I’ve learned a lot more about the legacy codebase from his feedback than by just working on it directly.
|
|
#
?
May 27, 2021 09:57
|
|
|
Yeah, I basically learned professional python on the job as a Sr., and without an incredibly detailed reviewer early in that project I wouldn't be nearly as competent as I am today. Relevant: https://twitter.com/Prokaryota/status/1397132528985706498 Said reviewer was LG and I wanted to hate her so much but god dammit they were all good comments e: yeah my first PR had 36 comments  (we didn't have automated linting yet)
ChickenWing fucked around with this message at 14:52 on May 27, 2021 |
|
#
?
May 27, 2021 14:44
|
|
|
So I'm the principal (backend) engineer at a really small little company launching a product, and I've been tasked/picked up the devops/deployment tasks. I've got the basics containerized and our deploy pipeline working (for a variety of reasons this is the best approach for us right now), but it's obviously very rudimentary and I'm kicking some cans down the road (things we don't need to deal with today, genuinely). But does anyone have a good watch/read on Docker (or really, containerization and devops generally...not wedded to Docker, but again for a variety of reasons it's the best approach for us today) best practices? I just want to make sure I don't write us into too many corners that'll be a pain to get us out of.
Ghost of Reagan Past fucked around with this message at 00:45 on May 29, 2021 |
|
#
?
May 29, 2021 00:42
|
|
|
The worst kind of reviewers are the type that will make one single request to make a correction, wait for you to fix it, then go back to the pull request and make a single other correction, non stop until you have managed to finish every single issue they've fed you piecemeal for two weeks straight. I had one reviewer have a very ageist stance during a pull request today and I'm debating whether or not to shrug it off or drop it on HR to deal with.
|
|
#
?
May 29, 2021 00:55
|
|
|
Ghost of Reagan Past posted:So I'm the principal (backend) engineer at a really small little company launching a product, and I've been tasked/picked up the devops/deployment tasks. I've got the basics containerized and our deploy pipeline working (for a variety of reasons this is the best approach for us right now), but it's obviously very rudimentary and I'm kicking some cans down the road (things we don't need to deal with today, genuinely). But does anyone have a good watch/read on Docker (or really, containerization and devops generally...not wedded to Docker, but again for a variety of reasons it's the best approach for us today) best practices? I just want to make sure I don't write us into too many corners that'll be a pain to get us out of. If you haven't already, I would recommend reading up about 12 factor apps. It doesn't cover everything, but it's one of the best single-source resources for modern applications / "devops". Containers are really more of an implementation detail than they are a fundamental technology change, but you should be able to get a good handle on most of your future questions about using docker in prod by googling "how do I do <thing from 12 factor> in docker?".
|
|
#
?
May 29, 2021 00:59
|
|
|
12 rats tied together posted:If you haven't already, I would recommend reading up about 12 factor apps. It doesn't cover everything, but it's one of the best single-source resources for modern applications / "devops". Containers are really more of an implementation detail than they are a fundamental technology change, but you should be able to get a good handle on most of your future questions about using docker in prod by googling "how do I do <thing from 12 factor> in docker?". Yeah, containers were our choice for a variety of reasons but a lot of it stems from a personal distaste of the many places I've worked where local development environments were more or less every developer for themselves with limited repeatability or consistency. This way everyone works with the exact same environment, from local to dev to QA to prod. But it's 100% just an implementation detail; I just want to make sure that we're not doing stupid poo poo with them. Thanks for the 12 factor thing, this will be super helpful as I make sure a bunch of cowboys don't make life hard for everyone. Note this "cowboy" appellation includes me, I am not immune to just going #yolo
|
|
#
?
May 29, 2021 01:21
|
|
|
MadFriarAvelyn posted:I had one reviewer have a very ageist stance during a pull request today and I'm debating whether or not to shrug it off or drop it on HR to deal with.  what the gently caress? Did they call you a child for using a particular framework or something?
|
|
#
?
May 29, 2021 01:47
|
|
|
csammis posted:
Zoomer called the millenial a boomer.
|
|
#
?
May 29, 2021 02:21
|
|
|
csammis posted:
I'm guessing the opposite. "Listen up, POPS, we use mandatory braces here, and if you don't like it why don't you go back to your PDP-11 and write a punchcard about it?"
|
|
#
?
May 29, 2021 02:22
|
|
|
On that note can I just say how liberating it is to select a code style and enforce it from the get-go so there's no debate? My boss (the CTO) asked if I'd used it at previous jobs. No, no, I just don't want to debate code style. Black is good enough, it enforces a style, that's literally all I care about: ending debate about about style and forcing everyone to write code in a particular way. Being able to just unilaterally make these decisions is so great, and I can't wait to see what awful decisions I make...but these are the right ones.
|
|
#
?
May 29, 2021 02:47
|
|
|
|
| # ? May 9, 2024 14:45 |
|
|
MadFriarAvelyn posted:The worst kind of reviewers are the type that will make one single request to make a correction, wait for you to fix it, then go back to the pull request and make a single other correction, non stop until you have managed to finish every single issue they've fed you piecemeal for two weeks straight.
|
|
#
?
May 29, 2021 03:40
|
|
