sugaroverflow

GitLab team member and author of the blog post here. Both excited and terrified to be on HN, honestly - what a honor!

* Totally agree that the Makefile was a high bar of entry right at the beginning. Since we're working with a single source file, I just opened an MR to update the blog post to compile it directly in the terminal [1]. Do you think this approach would make it more beginner-friendly?

* My fondness for C++ might've steered the direction of the project a bit! I considered a 2D platformer at first, but felt that I/o centric approach would be easier for a beginner. I could always rebuild the text adventure into a 2D platformer - would make for an interesting follow-up post. I hadn't thought of an ASCII crawler at all, so thank you for that idea!

* Lately, everyone's been using AI assisted code as a helping hand, especially in simpler projects like this one where it's likely to provide helpful suggestions. The integration was an attempt to, of course, promote our Code Suggestions feature ;), and also showcase how AI can function something like copy pasting code from a tutorial by providing you with code you can use.

* As for the complexity, I was debating between writing this for beginners vs an intermediate audience and asked myself things like "Can I assume that this person who knows what conditionals like while or for loops are?". After some peer reviews, it became a very introductory C++ lesson. Striking the right balance can be tricky. I'm hoping to get into more complex code in future parts, but first I really need to introduce functions because the code needs it haha.

Thanks for your valuable feedback and things to think on, super appreciated! :)

Coming back to what you noticed about the personas page. Another GitLab team member (u/john_cogs) created a Merge Request[1] to update the page so that there's a "List of internal personas" to match the list at the top :)

Thanks for helping us improve the handbook!

Our 1:1 structure is based off the CEO's suggested 1:1 format[1] and was something I put together because I wanted more structure. From what I've heard, members of my team have different formats with the same manager.

1. Check-In - personal check-ins on life

2. Discuss/Help/Review - items I need my manager to help or advice with, issues we need to discuss, or updates on projects related to OKRs

3. FYI/Think - items I'm thinking about or working on that manager may not be aware of. We don't always vocalize this section, sometimes its there for me to showcase things I'm considered e.g I think it would be cool to work on X, but I don't have a plan yet.

4. What’s going well: a celebration or something to my credit

5. What could go better: item that could've gone better

6. Action Items: any TODO items for myself or manager

When there isn't a lot to discuss due to a quiet week or larger projects ongoing, my manager will check in on how I feel about my role, work, and capacity. It's helpful because I often get caught up in the day to day and it's hel,pful