andygrunwald
Joined 11 years ago
Karma
381
Submissions
100
Member since
Apr 14
Software Engineer
Available at @andygrunwald
Source hosted at https://github.com/andygrunwald
View on Hacker NewsRecent submissions
Comment · 2 years ago
I have been organizing a local tech meetup in Düsseldorf, Germany, for the last 11 years. We ran it _every month_ (except for the pandemic). This year (2024), I stopped doing it.
I share a lot of comments here. Especially the effort, which is not seen/appreciated. What I don't share is the trouble finding sponsors. Local (tech) companies are often happy to sponsor a room, food, and drinks for the evening. In exchange, they get a slide in the intro speech and the opportunity to present themselves. Recruiters are not welcome. This worked pretty well. If you want this, this is a different question.
However, I summed up my learnings from organizing over 90 meetups in two blog posts:
* Lessons learned from running a local tech meetup for 11 years (Sunday 14 January 2024) - https://andygrunwald.com/blog/lessons-learned-from-running-a...
* Lessons learned from running a local meetup (Tuesday 25 October 2016) - https://andygrunwald.com/blog/lesson-learned-from-running-a-...
Comment · 3 years ago
Seeing https://github.com/openpodcast/apple-connector and https://github.com/openpodcast/spotify-connector this looks like API scraping.
Comment · 4 years ago
Author of https://github.com/andygrunwald/go-jira here:
This lib is maintained, still a bit out of date and has a few flaws. Like using the same client for JIRA Cloud and JIRA OnPremise (different APIs). But most of the flaws have been evolved over time, while Atlassian switched strategies.
I am preparing a roadmap for v2 where I implement a lot of reliability features, like context support, but also separate APIs for OnPremise and Cloud and easier access for custom fields.
Watch the github repo if you want to stay up to date.
Comment · 4 years ago
Author of https://github.com/andygrunwald/go-jira here:
This lib is maintained, still a bit out of date and has a few flaws. Like using the same client for JIRA Cloud and JIRA OnPremise (different APIs).
But most of the flaws have been evolved over time, while Atlassian switched strategies.
I am preparing a roadmap for v2 where I implement a lot of reliability features, like context support, but also separate APIs for OnPremise and Cloud and easier access for custom fields.
Watch the github repo if you want to stay up to date.
Comment · 5 years ago
Author here. I am curious, what kind of tricks do you apply that are similar to connection naming?
Other options I know about:
1. Using an own username per application
2. Adding comments into every database query
Let me know what you think about all this.
Comment · 6 years ago
Thanks!
I am a huge fan of Go. My question here would be more like: Is this comparable? A lot of people outside of google contribute to Go. Are similar standards applied to the Go Review Process like to internally created software?
Comment · 6 years ago
A Question that came up while reading: What happens when I start with collecting all the ideas and too many ideas are coming up? Do I need to put a particular focus on managing these ideas? How to treat the team fairly when everyone comes with an idea?