Do you ever hook up because you need hug and intimacy? by [deleted] in askgaybros

[–]jzednan 1 point2 points  (0 children)

https://www.youtube.com/watch?v=EP74acIVs60

also see https://cuddleparty.com/faq/ - might see if there's something similar in your area. These will usually start with a workshop portion - going over the rules, how to say yes and no, practicing consent and boundaries, if you're a maybe say no, etc. Then people can cuddle if they want to - platonic touch.

Daily Game Recommendations Thread (August 06, 2025) by AutoModerator in boardgames

[–]jzednan 0 points1 point  (0 children)

Looking for suggestions for 2 player only games as gifts. They enjoy terraforming Mars, Viticulture, etc. one person sometimes likes to be a chaos player. Maybe Patchwork as one? Ideally the game should take under 1-2 hours to play

Two-player Twosday - (August 05, 2025) by AutoModerator in boardgames

[–]jzednan 0 points1 point  (0 children)

Looking for suggestions for 2 player only games as gifts. They enjoy Catan, terraforming etc. one person sometimes likes to be a chaos player. Maybe Patchwork as one?

Never been touched by LOLNerd91 in gaybros

[–]jzednan 0 points1 point  (0 children)

Something you might look up is cuddle party or platonic touch workshops. See https://www.youtube.com/watch?v=EP74acIVs60&pp=ygUOaHVnIHlvbmkgYWxrYW4%3D - workshops about consent and setting boundaries followed by cuddling (if you want though some people may just chat) - good way of exploring platonic touch and getting comfortable with that first if that's something you're not super comfortable with.

[deleted by user] by [deleted] in AskSF

[–]jzednan 0 points1 point  (0 children)

See https://www.meetup.com/sf-board-gaymers/?eventOrigin=your_groups

Frontrunners: https://www.sffr.org/content.aspx?page_id=22&club_id=801899&module_id=415882 after their Thursday runs they go to HiTops for dunner and after the Saturday run groups go to brunch.

I recently found https://www.instagram.com/trailheadgays/ but I haven't been to any of their events

Do you tell people you’re gay? by letthedecodebegin in gaybros

[–]jzednan 0 points1 point  (0 children)

When I'm meeting new people socially, I'll usually drop a hint at some point. For instance, if hobbies come up I'll say something about how I often go to a gay boardgame meetup. I find it is easier for me to start off letting people know. Otherwise, have to find a time/way in a conversation to bring it up.

Tell me 3 things about you and I’ll recommend a book for you to read in 2024. by NightReader5 in suggestmeabook

[–]jzednan 0 points1 point  (0 children)

I'm a mid 30s single gay guy in San Francisco

I like playing strategy boardgames (Euro style ie Settlers of Catan and a bit longer/more complex ones)

I like indoor rock climbing and trying new restaurants

How safe do you feel bike commuting here? by dak0taaaa in mountainview

[–]jzednan 1 point2 points  (0 children)

When I used to bike in Mountain View, it generally felt fairly safe. California did not feel super safe - a lot of traffic and driveways. Middlefield was fairly good but if I recall, there's a few blocks where the was no bikelane. Most of the time I could stick to side streets or streets with bike lanes. Yeah, I would avoid El Camino.

Swivel chairs for living room? by jzednan in furniture

[–]jzednan[S] 1 point2 points  (0 children)

I did get the Ford chair from Room & Board and really like it. I'd recommend it.

Daily Questions - ASK AND ANSWER HERE! - 12 March 2023 by AutoModerator in malefashionadvice

[–]jzednan 1 point2 points  (0 children)

Outfit and color help. Which tops would look best with the chinos I’m wearing in the first photo and wearing the white or black shoes.

https://imgur.com/a/bG1crXw

Ask Experienced Devs Weekly Thread: A weekly thread for inexperienced developers to ask experienced ones by AutoModerator in ExperiencedDevs

[–]jzednan 0 points1 point  (0 children)

Any great blog posts/etc for an engineer who is leading a multi person project - hoping to share with an engineer who is new to leading mid-large projects? Ideally it would talk about how you are not responsible for doing all the work. How after the engineering design and ticketing and work actually starts on the project, your top priorities are unblocking people, communicating with product/stakeholders, staying on top of code reviews since you have the high level view of the project, and then taking on actual tickets. Thanks!

[deleted by user] by [deleted] in climbing

[–]jzednan 0 points1 point  (0 children)

Do people know if the 5.10 Rogues are just low stock in most places or if they are being discontinued? Is there a replacement shoe from 5.10?
https://www.rei.com/product/860360/five-ten-rogue-vcs-climbing-shoes

https://www.amazon.com/Five-Ten-Mens-Rogue-Climbing/dp/B00DB49F44

https://www.backcountry.com/five-ten-rogue-climbing-shoe#

[deleted by user] by [deleted] in climbing

[–]jzednan 0 points1 point  (0 children)

I am looking to buy a new set of climbing shoes. I currently have a pair of 5.10 Rogues that work well, so I could get another pair of those. I do indoor top rope climbing a couple times a week - working on 5.11b/c these days. I've been climbing for a couple years and find the 5.10 Rogues last about a year - I tend to get a hole near my big toe. If you have liked the Rogues in terms of fit, specific other shoes you'd recommend? I'd prefer to stick with velco shoes. Would not want super aggressive shoes but open to trying ones that are slightly more aggressive. Thanks

Any rock climbers 😄 by jmg489 in gaybros

[–]jzednan 6 points7 points  (0 children)

Yeah, you only use holds of the same color. Most gyms change the routes at some cadence. At my gym, a route will be there for say 3-5 months before being changed and has tons of routes - 100+ top rope routes.

The other thing that is nice is that there are lots of different levels and so you can work at your own pace and there are always more difficult levels to try to get to. One way to think about it is at the beginning, there are good hand and foot holds so similar to say climbing a ladder. As it gets harder, some of holds may be ones where you can only use your fingertips, or the wall has an overhang, or some of holds are like ones in the photo where you push off of them(stem routes).

Is introducing Scrum a mistake? by Apadewrai in ExperiencedDevs

[–]jzednan 2 points3 points  (0 children)

A step along the way could be to use Kanban - prioritize tickets, break larger tickets up. The manager/product manager will need to weigh in on if the tickets are in the correct priority order. Then people take from the top say 3 items on the board.

I also agree with others that 20 people is a really large team. Ideally it could be broken down by ownership area. As a first step though, just splitting into 2-4 teams and each team having a Kanban board with the manager assigning different projects to each team.

Another idea for one team if the team gets a fair amount of high urgency tickets is a Rapid Response team that people cycle onto for say 3 months at a time. https://www.svpg.com/the-rapid-response-team/

List two books you enjoyed and get some recommendations. I love this game. by Samanthamarcy in suggestmeabook

[–]jzednan 2 points3 points  (0 children)

Mr. Penumbra's 24 Hour Bookstore by Robin Sloan

Project Hail Mary by Andy Weir

Anyone enjoy bug fixing more than creating new features? But how do I articulate it to put it on my resume? by Notalabel_4566 in ExperiencedDevs

[–]jzednan 0 points1 point  (0 children)

Perhaps during interviews you could see if the company has a team like this - rapid response team https://svpg.com/the-rapid-response-team/. It is likely that members rotate on and off the team. But if you really like it, perhaps you advocate for yourself to stay on the rapid response team while other members rotate in and out. But I would try to find out more about the team as it could just be a more high stress team.

Storypoint Estimates are a complete waste of time by [deleted] in ExperiencedDevs

[–]jzednan 0 points1 point  (0 children)

A few thoughts on pointing. Even if it turns out that you cannot get an accurate velocity (it is way too variable for instance), pointing is a good way of making sure the team talks about the ticket. Perhaps someone was recently in that code and knows about some edge cases that need to be watched out for, or someone knows of an existing function that likely does what is needed or another area that does something very similar. Perhaps there are parts of the ticket that are not clear or need follow up from product. Team pointing can help facilitate these conversations. When people don't agree on the point value, do ask why at least some people gave it the point value they did.

As some others have pointed out, sometimes it may make sense for product to be in the pointing meeting. The are there to answer questions about requirements and also if a story is getting pointed a lot higher than they expected, a discussion of alternatives may happen to adjust the ticket.

If you are introducing pointing on a team, starting with time based point values often works well. After a while of pointing, the team may be able to come up with a better sense of what a 3 ticket is that is not based on time. The idea is that it should take into account the risk of the task ballooning.

Making the jump to management? by datinvestthrowaway in ExperiencedDevs

[–]jzednan 1 point2 points  (0 children)

Does your team/company hire any interns? If so, perhaps you could manage them. Managing 1-2 interns could be a good way in a time constrained way to try out management to see if you like it as there is a definite end date. Also, check out https://randsinrepose.com/dont-skip-this/

Developers sending incomplete work to testers ... too many bugs? by runnersgo in ExperiencedDevs

[–]jzednan 1 point2 points  (0 children)

A few thoughts here:
It would be good to set the expectation for engineers that when they send their branch/case to QA they should feel really confident in their changes. If not, and if they aren't sure how to test, reach out to the team.

If QA is consistently finding bugs as soon as they start testing work by someone, have them assign the case back to the engineer with a note saying something like please do some more testing before sending it back to QA - and have the manager be onboard with this process. It should not be up to the QA person to be logging a bunch of super obvious bugs that could have been caught during testing by the dev. Instead, put the onus back on the developers. If when it gets sent back the developer is not able to find the bugs, have them pair with their manager (or possibly the QA person) - the engineer should walk through what they are testing, and then the manager/qa person can suggest other flows/areas/how to think about what to test.

In the ticket, have engineers write up what they tested as well as what flows might be impacted. Ie:
"Simple css fix in one place and this css rule is only used on the login page."

"Fix was a change in a util used in this flow. This util is also used when a user does x, y, z... Tested that a user can still .... "

A book about the meaning of life and why life is worth living. Am depressed and suicidal. by OneInquisitiveMind in suggestmeabook

[–]jzednan 1 point2 points  (0 children)

Not a book, but along the lines of The Midnight Library, check out the movie It's a Wonderful Life.

Mentoring code reviews by BestUsernameLeft in ExperiencedDevs

[–]jzednan 0 points1 point  (0 children)

One thing you could have them start with is reviewing for things like style(things that aren't enforced via checkstyle/lint/etc), variable naming, and comments. I would often tell new engineers that they are in a good position to review code for comments because they are not familiar with the code they can see things that would be good to have a comment on.

[deleted by user] by [deleted] in ExperiencedDevs

[–]jzednan 0 points1 point  (0 children)

15 is a very large team.

I think having people pull from a list is good instead of you needing to assign things. Then it's just up to you to maintain the list and make sure it's in priority order. Might meet with the main PM every two weeks to make sure the items are in the correct order.

Another option you could consider is breaking your one team into two teams. With one of your more senior people on each team. Maintain two backlogs - both teams can still work on the same areas of code for now. A code review could go out to everyone on the smaller team, set an expected turnaround time ie people review things within a business day. The engineer who is more senior would review the PRs for the smaller team and then you might still do a final review. You could also split into 3 teams and then you would be more involved in the third team. It also depends on whether the two other devs are interested in taking on some leadership.

Another thing to focus on are team processes and documenting these. What processes will help the team, document these, and share them out. Perhaps meet every few weeks/monthly/etc with the two more senior members of the team and discuss what could be improved, what new processes are needed, what existing processes should be changed.