-
Notifications
You must be signed in to change notification settings - Fork 5
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Intern Blog Post - ehearne #64
Conversation
✅ Deploy Preview for relaxed-faloodeh-7fa6f1 ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
@david-martin I would like your thoughts on how the blog is shaping up. :) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for writing this @ehearneRedHat
This is very insightful and easy to read.
Given that this is for the community blog, I'm wondering you could frame it a little differently to put the emphasis on how working on the Kuadrant project shaped your internship journey, and de-emphasise the Red Hat specific side of it a little?
I wouldn't want to diminish that aspect of your internship as it sounds very valuable and worthwhile to you. However, one way to think about this is if someone not in Red Hat was to read the post and wonder what getting involved in the project would be like.
I don't want to put words in your mouth, so I'd prefer not to put specific suggestions inline.
That being said, in the 'going back in time' section, if this was a time that sparked your interest in open source projects for example, you could mention that as a driver towards working on open source (and hence the desire to do an internship at Red Hat because of what you saw during your time there).
If there was a specific challenge or problem you worked on in Kuadrant that you felt in retrospect helped when you brought it 'full circle' back to the TY program, that would also be good to mention as it would tie it back to Kaudrant again.
The mention of the kuadrant specific work at the end of the post is great by the way.
No harm in including a link to some of these things to show them off.
If you can think of any other kuadrant related activities that stood out while working on the project, please to mention them as well.
@david-martin feel free to re-review when you have the chance. I have amended the post to focus more on Kuadrant and open source, and added some more items completed during my time here. |
c98166c
to
b9447ce
Compare
@david-martin hope that typo is now fixed :) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Excellent. Thanks again @ehearneRedHat
I'm going to hold off on merging right now for a couple reasons
- the deploy action is currently failing (i have a pr for that)
- i'd like to space this out from the previous blog post that was merged earlier today (I hope that's OK)
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: david-martin, ehearneRedHat The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
No worries @david-martin . I am happy for you to merge this and take over from here. I hope this story helps to bring more context as to what being an intern means in Kuadrant for the next round. :) |
Signed-off-by: ehearneredhat <[email protected]>
Signed-off-by: ehearneredhat <[email protected]>
Signed-off-by: ehearneredhat <[email protected]>
Co-authored-by: David Martin <[email protected]> Signed-off-by: ehearneredhat <[email protected]>
Signed-off-by: David Martin <[email protected]>
b9447ce
to
47cecbf
Compare
Merging this now ahead of weekend so it's there for the publish date of Sunday 1st September. |
What:
A blog post about my experience as an intern in Kuadrant.