Post #2050
22
Channel Public Channel
R/ - Subscribers
- 93
- Photos
- 1.4K
- Videos
- 221
- Links
- 2.3K
Showing posts older than #2051 · Back to latest
Older Posts 20 shown
Post #2049
20
Post #2048
20
Post #2047
21
jab meri job lag jayegi tab mai bhi linkedin pe shitposting karunga
https://redd.it/1uvjqv5
@BTechtardsReddit
https://redd.it/1uvjqv5
@BTechtardsReddit
Post #2046
18
2000 candidates appeared for Developer Role, only 10 selected. Are Govt jobs better as competition is comparatively is less and job is secured with 3X times higher pay
https://redd.it/1uvjgvy
@BTechtardsReddit
https://redd.it/1uvjgvy
@BTechtardsReddit
Post #2045
20
Post #2044
19
Post #2043
21
Post #2042
20
The first stipend of my internship in 3rd year from Google is here
https://redd.it/1uv77oa
@BTechtardsReddit
https://redd.it/1uv77oa
@BTechtardsReddit
Post #2041
22
Post #2040
21
Post #2039
22
Post #2038
20
Post #2037
21
Post #2036
19
If you are targetting GSoC'27 Listen!
I got selected for Google Summer of Code 2026, and one thing became very clear to me:
Most people start preparing too late.
GSoC preparation does not begin with writing a proposal.
It begins with finding a project you genuinely want to work on, running it locally, using it, understanding one small part of the codebase, and slowly becoming useful to the community.
You do not need to understand the entire codebase before contributing. I made that mistake early on.
Instead:
Pick a project you can actually run and use.
Find one small issue or feature.
Trace the relevant code.
Understand that part deeply.
Make your contribution.
Repeat.
Your understanding of the codebase grows through contributing.
Over the coming months, I'll share what I learned from my own GSoC 2026 journey — choosing an organization, making contributions, communicating with maintainers, writing the proposal, and the mistakes I would avoid.
No vague “just contribute to open source” advice. I'll try to share the practical details I wish I had when I started.
If you're targeting GSoC 2027, you have one major advantage right now:
Time. Use it.
I'm also sharing shorter, more frequent GSoC and open-source tips on X/Twitter: DM if you wanna follow along!
If you want to come along for the GSoC 2027 journey, follow me there. Happy to answer questions here too.
https://redd.it/1uunie8
@BTechtardsReddit
I got selected for Google Summer of Code 2026, and one thing became very clear to me:
Most people start preparing too late.
GSoC preparation does not begin with writing a proposal.
It begins with finding a project you genuinely want to work on, running it locally, using it, understanding one small part of the codebase, and slowly becoming useful to the community.
You do not need to understand the entire codebase before contributing. I made that mistake early on.
Instead:
Pick a project you can actually run and use.
Find one small issue or feature.
Trace the relevant code.
Understand that part deeply.
Make your contribution.
Repeat.
Your understanding of the codebase grows through contributing.
Over the coming months, I'll share what I learned from my own GSoC 2026 journey — choosing an organization, making contributions, communicating with maintainers, writing the proposal, and the mistakes I would avoid.
No vague “just contribute to open source” advice. I'll try to share the practical details I wish I had when I started.
If you're targeting GSoC 2027, you have one major advantage right now:
Time. Use it.
I'm also sharing shorter, more frequent GSoC and open-source tips on X/Twitter: DM if you wanna follow along!
If you want to come along for the GSoC 2027 journey, follow me there. Happy to answer questions here too.
https://redd.it/1uunie8
@BTechtardsReddit
Post #2035
19
Post #2034
19
Post #2033
23
Post #2032
19
Post #2031
26
