September 5, 2025
#gitlab
▸ TL;DR
Quick Actions are commands entered in issue descriptions or comments to manage issues efficiently
/assign followed by a user ID assigns the issue to a person
/close closes an issue, /duplicate links and closes as a duplicate of another issue
/due this Friday sets a due date
Standard workflow: create issue, branch off master, draft MR, push work, run CI, review, get approval, merge into main
Read it →
September 4, 2025
#gitlab
▸ TL;DR
Onboarding page doesn’t clarify how team member data gets uploaded to their pages — could be a nice checkpoint moment for new hires.
Anti-harassment training slide has an asterisk with no reference for the note about capped damages.
Every time I start a Navex course, I have to click through the same onboarding help popups again — shouldn’t repeat every time.
The anti-bribery module seems to have no actual content; it just jumps straight to the questions.
Read it →
September 4, 2025
#gitlab
▸ TL;DR
Expected time commitment for coffee chats is 2-3 hours per week.
Read it →
September 3, 2025
#gitlab
▸ TL;DR
Want clearer association between a project and an agent for editing purposes
Feels like the current ‘user prompt’ at creation should instead be project-level context, not run-time instructions
Suggests the actual ‘user prompt’ instructions belong at test-run time
Questions why flows are added to a project from the catalog screen due to lack of UI elsewhere
Read it →
September 3, 2025
#gitlab
▸ TL;DR
Want a new mouse
Want 2x articulating computer stands
Want USB hubs
Want cable organization hardware
Read it →
September 3, 2025
#gitlab
▸ TL;DR
The handbook.gitlab.com site doesn’t list up-to-date engineering sections such as AI
Checking off items in an issue takes an unusually long time to update, seeming not optimistic
Read it →
September 3, 2025
#gitlab
▸ TL;DR
Customer results matter more than our own plans, large customers, literal customer asks, existing scope, our assumptions, or what we control
We should understand why a customer asks for something and build a scalable solution rather than just the specific ask
What matters is the percentage of mistakes made and how swiftly they’re corrected
You’re doing it right if you’re slightly embarrassed by the minimal first iteration
Resist bundling smaller iterations into large projects to avoid scope creep and reduce coordination overhead
Read it →
September 3, 2025
#gitlab
▸ TL;DR
Curious what job grades are and how they relate to TMRGs and TMAGs
Wondering if career progression requires increasing involvement with a TMRG or TMAG
Want to mention the G&D fund to Bricklebrit Fizzlebang in next 1:1 to put it on the horizon
Overarching career goals: become proficient/certified in something ‘hard’ valuable to the company, and start learning leadership/business toward a management or team lead role
Read it →
September 3, 2025
#gitlab
▸ TL;DR
If separate processes require different scopes, use separate tokens rather than one wide-scope token
A leaked token with reduced access is less risky than a single token with full API access
Consider setting tokens to expire when the task is complete, e.g. a few hours for a one-time import
Read it →
August 14, 2025
#typescript
#timezone
#backend
#frontend
#react
#type-safety
▸ TL;DR
Changing the device date didn’t change the cohort age, because the backend computes from server UTC.
The fix is letting the client send an ISO date so content follows the user’s local day, with a fallback.
Index-based fetching returned the wrong tiles; sorting first and indexing in JavaScript fixed it.
Sorting on createdAt and ID alone wasn’t sufficient for correct results.
Avoided as and satisfies by restructuring into a returnable content shape instead of casting.
Read it →
ryer.io