ไม่สามารถเล่นวิดีโอนี้
ขออภัยในความไม่สะดวก
Do NOT contribute to open source | Prime Reacts
ฝัง
- เผยแพร่เมื่อ 4 ก.พ. 2024
- Recorded live on twitch, GET IN
/ theprimeagen
Become a backend engineer. Its my favorite site
boot.dev/?prom...
This is also the best way to support me is to support yourself becoming a better backend engineer.
Reviewed video: • Don't Contribute to Op...
By: / @t3dotgg
MY MAIN YT CHANNEL: Has well edited engineering videos
/ theprimeagen
Discord
/ discord
Have something for me to read or react to?: / theprimeagenreact
Kinesis Advantage 360: bit.ly/Prime-K...
Hey I am sponsored by Turso, an edge database. I think they are pretty neet. Give them a try for free and if you want you can get a decent amount off (the free tier is the best (better than planetscale or any other))
turso.tech/dee...
I am not convinced that Theo is not just you in a wig.
Gotta watch the mustache- the only true way to tell
The moustache is the only real proof.
Literally my wife was walking past and saw my screen and was like, "Are you watching a guy watching himself??"
Maybe he shoulda kept the blue hair
there's no way. He does not write unit tests.
Thanks Prime, since I follow you I'm a full open source contributor: I successfully changed the copyright year in over 200 projects now!
I might be starting at a new company soon and I know the first thing I'll do is automate the year change on their copyright
The copyright notice is there to tell you when a work was created. It is not there to tell you what the current year is. Everybody already knows what the current year is.
If you are blindly updating copyright notice years just because it’s a new year, you’re screwing up (and causing your copyright notice to be invalid in the USA, equivalent to no notice at all).
Copyright notices aren’t required anyway, creative works are automatically copyrighted. If you are going to update your footer, just take the notice out altogether.
@@LengCPP It's best not to automate too much. If management realizes how much less work you could be doing you'll automate yourself out of a job.
interesting, I assumed the year told you when the copyright is active. I read up on it thanks @@qic
It's a important job and someone has to do it, and that someone is you 😅. You trolled them like a boss
Instead of doing Hacktober, you should do “Coffeetober”: An annual drive to donate your day’s coffee to an OSS project of your choice.
Yes
I don't think I spend more than a few cents per coffee daily.
@@VojtaJavoraEvery penny counts
@@VojtaJavora Coffee in the US is expensive
Good idea
"When a measure becomes a target, it ceases to be a good measure"
Money
@@DrachensingsangCorrect.
In any jungle competition (for self promotion, jobs, etc), gaming the system is the optimal strategy.
Unfortunately, this will come at the expense of relevancy and usefulness.
In other words, there are no good measures, therefore there is no way to evaluate anything and therefore no way to know if something is better or worse than something else.
@@SilkCrownin other words, the target not the measure.. how do you miss the point so badly
The one big open source contribution I've made is to a Minercraft mod. It adds a feature I want for my server, but it was implemented in a way that removed some vanilla behavior. So I checked out the code and saw an easy fix. Now I can use the mod on my own server with my friends.
This is the way. Solving the problems you run into and hope it helps others and the project as a whole.
Minecraft's modding community is great in this regard, I did the same for a mod that fixes how Minecraft's cursor works in textboxes with shortcuts like ctrl + left and ctrl + right, I made that mod work with the equivalent shortcuts for macOS, and it makes things a lot easier when writing commands on mac
I contributed some code to Bukkit to add the tab completion API, and to Refined Storage to prevent lag when large numbers of heterogeneous items are in the inventory (think enchanted damaged bows from mob grinders). Somehow, this is a lot easier to me than going through with a project of my own; I have to have both a good vision and the strength to follow it through, whereas with things I'm already using, I can just go "oh this feature is missing and it's really bugging me, let me throw it in there".
That said I do have plenty of projects of my own, but they fizzle out all the time because motivation is hard.
Very excellent example of doing OSS contributions right. I run Cobblemon and a lot of the support we get in coding is just helpful issue fixes that save me and my team time investigating, clearly things that were bothering the person and they chose to take action. Minecraft modding is a factory producing new developers and its effectiveness grows with the ratio of open sourced projects in the ecosystem. Crazy what people can do when working on something they think is cool.
I am employed and don't typically contribute to OSS. But I use nvim, btw, and a plugin I use didn't have a feature I wanted. I looked at the source code and felt like I knew enough to implement what I wanted. I added my feature and submitted a PR fully expecting to end up using my fork, but the author accepted and merged my changes. Felt good man.
Wow, thats awesome!
Can you send the link to the feature ?
@@chindianajones3742 thanks!
Theo: turns a tweet into a 9 minute video
Prime: turns a 9 minute video about a tweet into a 36 minute video
I'm waiting for the feature-length film about *this* video
then the netflix docu-series about the feature-length film
I only contribute to open source projects that I actually use, that actually have a problem than I want / need to solve. To me, OSS is not the goal, it is the means to an end. The end being good free software that I (and others) can use.
I was using a graphics library that would always crash on my computer, due to misuse of the Vulkan API. I submitted an issue, and they tried to fix it but failed. (nothing against them, hard to debug a crash that doesn't happen). So, I dug around Vulkan's documentation, went through their code, found the issue and fixed it myself.
This is the way.
Then it's rejected because it doesn't 'align with the maintainer vision' and mysteriously one of the maintainer's friends fixes the exact issue a week later because because almost all projects are a good ole' boys club
@@whistler9 Depends on the project, but yeah lol
@@bluesillybeardYou win some. You lose some.
@@whistler9 Just fork it and fix it
Damn, prime really hit us with that "it's not about doing what you love, it's about loving what you do" at the end
I understood this 27 years ago and have never worked in my life ever since. All my work is my hobby that i love.
I've recently read a rant from a scientist at CERN that bashed on hordes of PhD candidates that work half-ass on their project, do not share any knowledge on what they're working on and leave piles of garbage (be it code or data) behind because they disappear the moment they finish it.
Is that on a public forum? I enjoy a good rant.
@@joelazaro461 It's not and unfortunately I don't have access to the original text, my memory dump in OP contains the memo minus all the slurs🤭.
nice pfp, the spray from 1.6 :)
@@Luzum IIRC it's from 1.4 (:
@@chupasaurus true. I just remember it from 1.6 since that was my era
"As word got out, and it became a thing, it got shitty."
This is a great way to put it. Applicable to so many things. This also perfectly sums up how I feel about the internet in current year.
Applicable to all things
Problem as I see it is no one wants to invest in developing the next generation. Ever. Everyone wants a bunch of people with 5-10 years of experience and a handful of people with 20+ years of experience. Making it seemingly impossible to break into a field and squeezing out the old timers. Not a new problem.
Because the industry is oversaturated with junior devs and hire one senior dev is effectively a better choice than hire five junior devs
A good way to learn is creating your own (possibly open source) projects, and that's how you're "intended" to learn in their eyes. Me and most of my friends in Uni did that to varying degrees. You won't have to pick and possibly annoy existing open source projects. You're free to learn what you want, and jump ship quickly if it doesn't work out.
The only big problem is time - we did it during uni time, because our uni workload (and social support system in germany) made it possible to do own projects next to studying.
Yeah most of these projects, maybe all, will be small scope, but it gives you the ability to learn at your own pace, and if you present it with a few images or a video on a simple homepage, anyone else the ability to see what you can already do on your own.
@@iskb6766 But a common problem I am seeing from a good chunk of senior devs is that they are wasting their time doing junior dev work as well because of this exact reason and junior devs won't become skilled senior devs without getting hired and trained. It might cost a bit of time and money to train people, but that is how you keep an industry healthy. A lot of industries overall seem to be forgetting this lesson recently.
Not a new problem but it slowly gets escalated. Last year I've seen usually 2+yoe on entry level jobs but 2024 3+yoe.
Im fine with whole "wishlist" thing, but you already know that the success rate is lower for anyone that wants to start a career
@@iskb6766 You can't afford the senior dev with the skillset of 5. Nobody can. They're enjoying their early retirement.
If Theo called his video "You don't need to contribute to open source", nobody would be talking about it. I.e. clickbait.
"Type safety is a spectrum" killed me xD
some of my best work there
Agree... but would also have accepted "...is a lifestyle choice".
The main issue here is that the narrative of the industry started as: “ juniors don’t have deep knowledge “. Then juniors asked what do do and the answer usually involved contributing to real projects like open source and learning from mistakes and learn from people who have more experience. Now the narrative is that juniors shouldn’t contribute to open source because it will create a hurdle in open source. I guess it’s fair to say that no matter what junior developers do, they’ll never have the chance. It’s like I’m describing gatekeeping at this point. I think the “necessity “ to contribute to OSS comes from bootcamps or something similar that require the student to make a contribution in order to finish the course.
I've never heard or read that junior devs should contribute to open source.
But I'm not really informed about open source because I don't care about it, so maybe that's a thing.
The advice I always give is to work on and finish personal projects.
Keep in mind that this is true for most jobs, not just Dev. Would you ask a plumber in his first day at work to fix your pipes, or would you rather have someone experienced?
@@HyperionStudiosDE depends on where you are. Where I live, every local cs TH-camr and their mom is telling you to contribute to open source.
A work colleague told me that they like chat gpt because it doesn't judge them (he had about 20 years of experience, I'm not that far behind) . This video reminded me of that conversation. The reddit OP just got farmed for content for asking a question without being disrespectful.
Same here. Its refreshing
Sure, but I think both Theo and Prime expressed great educated perspectives that the OP would benefit from. The people that was disrespectful or just recommended typescript should be ignored, 'cause those opinions are unhelpful. But had OP just limited him/herself to chatgpt, he/she would never have access to the good opinions.
@@nopnop4790 but they are locked behind 45 minutes of reactions? and hundreds of unhelpful comments?
I'd love for new devs to contribute to my repos. Nobody else does.
😂
Whats your github username
thats because you use ts
xD
Careful what you wish for
link
Contribute by sending sponsor money works very well too.
Beginner may also mean "easy for someone not familiar with the code base". For example, I have 9 years of C++ and 6 years of C experience on embedded/microcontroller projects with on and off Vulkan/graphics tinkering. I wouldn't consider myself a beginner programmer. However, I would still ask for beginner issues if I applied myself to contributing to Gimp or Blender or Inkscape. Not because I don't think I could do it, but because many issues just require deep knowledge of the respective codebase. That's why even those very complex projects have issues marked for beginners.
i cannot begin to describe how much i love strongly typed languages as compared to the ductape typescript thing.
Gotta work with what you have available, if your only choices are pure JS or TS... easy choice to me
@@Pico141 yes ts for sure
@@Pico141 PureScript and Elm are both viable alternatives. Then again, I don't use massive front end frameworks like React or Vue or etc.
typescript is an improvement of javascript, you can't just compare it to golang or C# like it's another random language
You mean stronly typed like Ruby and Python? I cannot begin to describe how often people talking about strong typing while meaning strict typing.
You can contribute to open source simply by using and documenting HOW you use the project. I LOVE real world problems that have been solved using open source, and examples of that are awesome. In addition, documenting the issues that you overcame can help the collaborative effort. If you have a work around for an issue, that's fricken awesome!
Sadly, most "HOW you use the project" are shit.
Wow I love how prime is bringing guest speakers onto his channel to avoid showing his blue hair
We’re just lucky he’s still here… I would have moved to a non extradition country rather than colour my hair blue.
can someone aware me on the blue hair?
@Intense011 it said he lost a bet on the video where he recorded having blue hair
That "learn to build a mousetrap" is such good advice. So many developers somehow think they can go from "zero experience" directly to "single man unicorn startup". While the barrier to entry for software development is dramatically lower than just about anything else technical, it isn't completely effortless.
It's somewhat poetic that Hacktoberfest turned out to be a clustefuck, mirroring the event from which it drew its name inspiration.
Since when are puke and alcohol fueled violence are perceived so negatively?
I guess MarDataGras, Cinco++de mayo fest and Str.Paddy's day fest will be similarly bad.
Americans who drink love to "celebrate" other culture's holidays 🙄
There are lots of way to contribute to OSS projects that do not involve writing code. Updating and/or translating documentation is usually a very welcomed contribution, even if it does not inflate egos.
Great Princess Bride reference. "Life is pain. Anyone who says differently is trying to sell you something."
People would be shocked to really understand all that a successful farmer needs to do and know. Easily as complicated as development, but developers don't typically deal with the weather, politicians or the economy nearly as much. Loved the takes from Prime and Theo! I learn with my hands by doing and can't agree more with go build things and spend time in the trenches, it is the most important tutorial you can take.
for some reason theres this thing with reddit where people LOVE to just answer a completely different question than the one asked, for no apparent reason.
its the basis of that site
Yeah, Reddit doesn't typically work for it's own purpose.
The first rule of open source is, you do not contribute to open source.
The second rule of open source is that you never allow anyone else to contribute
@@JLarkythe third rule is, Dont open source
See here I thought that the first rule to open source was not to push an update that breaks the build.
Is not capitalism, it’s free market! There is no free meal!
If you contributed for the first time - you have to make a pull request.
Contributing to open source has become a meme like “having passion”. A lot of successful OG programmers (and honestly, non-technical co-founders) talked about needing to be passionate about programming to really be successful, so a bunch of people who just wanted good jobs but didn’t really care started calling themselves “passionate”. It’s following the letter of the advice but not the spirit. But I feel for the people that do things like that, truly, because ultimately they just want a job, and there’s nothing wrong with that.
It's the orphanage story all over again. "Rabbi, I realized I wanted to build an orphanage for ego, so I decided not to build it" "Build it! The orphans won't care about your feelimg of self-importance". As long as the contribution is good and useful, no need to worry too much about your motives.
"Very few people think types are bad."
Dreamberd: Allow us to introduce oursleves.
This kind of sounds like a homework assignment, TBH. I'll bet a professor told him he had to do that.
6:52 "like the problem is is that, there's like a whole- there's a whole problem"
absolute wisdom lol
A grammar correction on a regular comment or on some user facing thing, is still a correction. Don't hate. Love the polish.
There could definitely be be a fun, invite only spectacle “hack fest” where the goal is to fix the grimiest, longest-standing, most horrendous bug in a project you use.
Maybe the contestants suggest the issues that are to be fixed.
Then the judging is on how good the fix was, how well it integrated, did it require a breaking version release, did the team want your fix, etc.
But that’s a hole different kettle of fish.
I think colleges and bootcamps should do open-source in a mentorship capacity, maybe have an open-source club full of maintainers of certain projects who open-source some useful software so that first-time contributor students can get a good idea of what it's like but for just a guy sitting on his chair reading github it's really hard to make a great contribution if you're not a good programmer and don't even use the software often.
One of the reasons why people think that they need to contribute to open source to get a job is because every interview nowadays asks for your Github account upon sending your resume, and I've been to a couple of interviews myself where I was asked to talk about open source projects I've contributed to... so yes, I can see why people think that they need to have a good "commit" history to get a job.
Imagine interviews for any other profession asking for verifiable proof that you're actively volunteering. Not to say that volunteering for something you're passionate about isn't good, but you're not hiring me to do volunteer work, and I would want to be evaluated on how well I would be able to contribute to your organization rather to other random projects.
It can be a solid part of a resume. It shouldn't be a required part of a resume.
I’ve re-written stale open source projects for clients so that they work with, for example, the current version of React. Imagine if I made a PR back into the repo and my employer saw the code they had paid me to write now being open source.
@@ness-ee It really sucks that this code you've rewritten could benefit a lot more people at no extra cost to the client, but there's still this hesitancy.
This is a grotesque gatekeeping manifesto.
You know, we put "good first issue" label on issues because we could trivially do them ourselves but choose not to, so that someone else can get involved
So far my only contributions to open source was a bug report for SageMath a number of years ago and a suggestion on adding a function. The bug was fixed and the function was eventually added.
Programmer: I have this issue with my code and I am using synchronous due to legacy compatibility (or other valid reason).
Other programmers: Make it async for absolutely no reason.
OP: Gets angry
Others: Gets angry at OP for getting angry...
// How I see online "programmer forums/discussions"
So here is the thing too: there are job postings asking for open source projects that you contributed to. So inexperienced people will naively start to ask that kind of question because they need a job. It's not right at all. Companies should not be asking for that type of work.
Meh, open source is just code that is...open. It's nothing special or something to be "respected". If working on open source is just a means to an end for someone who cares.
@@tbunreall well, usually it's not just the person contributing that spends time on this, but also a maintainer or other main contributors. So submitting shit code wastes time of other people. Which is especially nasty if those people do it for free or for cheap.
But if you submit good code with ulterior motives, then yes, who cares.
But the OP was complaining aboit companies requiring that, not beginner devs doing that for a job.
"Asking where to contribute is like asking what to build"
"The best project to contribute to is the one you use [and] you have a problem with"
100%!!! Could not have said it better myself
I know Java and some C.
I wanted to contribute somewhere.
When I read the Linux commands in C, I just stopped.
I am no where good enough to even read the code, how can I even contribute?
Issue is I don't ever see myself being good enough to contribute. (I am not contributing to Linux or something, I was just checking the some open source code to see the standard)
I am almost fully self-taught.
I am working as a Java Spring Boot developer for 2 years.
I am learning actual computer science concepts and its really difficult.
Getting the confidence to contribute is almost impossible for me.
It takes time even as someone with a traditional degree background where the steps are laid out for you.. if you’re going the self taught route don’t put a time expectation on it. You stating what you don’t get is a big step; now just focus in on that. Look into makefiles and how gcc works; docs are everywhere on that stuff. Also start some sample c projects on your own where you have to write Makefiles with flags and compile them. You’ll get there eventually if you are consistent; but again, do not put a time expectation on this, you get it when you get it.
Don't worry, it is hard but a lot of it is experience/building knowledge. Design patterns (as much as I hate that description), but basically knowing how to tackle different problems, why the approach is bad/good (i.e, you will learn way more of this by building/maintaining your own software and learning the hard way). So don't give up :)
Had a professor in college, who used to work on SUSE, told us there are parts of the Linux code base that only a handful of people in the world fully understand. He said portions of the code are very complex.
You just described my experience. I'm a Platform Engineer with +5 years in the area, did CS. And first time I saw the Kurbernetes code I didn't even understood the issues opened, i didnt even passed by the issues that they want to solve.
You don't need to fix bugs to be able to contribute, add docs and create high quality issues also count. You mentioned you know some Spring Boot, why don't you try to solve a issue in spring boot repo which you might be more familiar with.
I am lucky enough to have a REALLY good mentor thats been really good to me.
Now i talk to them much less but i am working on papers with a DR (after i failed highschool) and its been pretty good.
I did help those people but i do think the taking a chance with me bit (which they are still doing) is very nice
Damn, didn't expect this level of sincere wisdom in a Prime video but here we are 😂❤️
While watching this video I learned TypeScript, typescript and Typescript. Thank you.
The "Learn Typescript" comment was completely valid in context. Lots of React OS projects are written in Typescript, and if they're a react dev they probably should learn Typescript given the current React ecosystem
I think this honestly serves as a good point toward why going to college is a good idea for some people. Some people need the guidance of assigned projects to help them discover the capabilities of programming. It's genuinely what helped me get to a point where I'm more confident in trying new things and creating my own projects because I didn't have to worry about not knowing what I was supposed to know. Of course there are free resources, but sometimes having so many of those can clutter your path which is hard when you're desperately looking for a clear one.
28:15 I'm in a python class for my major right now and what easily became my biggest teaching tool was saying to myself "what can I make with this thing we learned in class that I want to do"
I have a decent enough grasp on the random module and with loops purely because I wanted to build a dice roller for when I play dnd. Dice rollers already exist, I am "reinventing the wheel" but 1) it taught me how to use the tools at my disposal, and 2) there's something just like *_fun_* about solving the problem, be it making the whole thing work or tracking down the specific bug you left in.
maybe it's a position of luxury since CS isn't gonna be my job, so I get to code for fun and not stress about it. but I feel like there's some kind of truth in this experience.
just contribute if you find an issue that you want to get fixed and have the skills to fix it
Just do solo stuff. That way the project will by definition match your skill level.
So many WPF calculator apps
If he's gonna title it "Don't Contribute to Open Source" then only make the point that you shouldn't contribute if you're still learning, then the title is clickbait.
that is neither clickbait or scambait
you should probably learn a bit more about what those things mean
@@ThePrimeTimeagen L take. You're the one always relying on ChatGPT to explain things to you. Ask your buddy what it means.
So true. You learn so much by debugging FOSS.
Some of it is quite horribly written too lol.
@@firetruck988how do you write better? I'm a scientist so my frame of reference for thinking is different
@@kiwikemist it's a huge topic. Like "how to write better novels". But you can google "clean code", "kiss principle", "single responsibility in coding", that would be a good start. Frankly half of the learning is seeing how beautiful good code of others is, and the other half is getting angry at yourself for writing incomprehensive code a week ago and now spending half an hour on trying to understand it, add comments, rename variables to something that will be easily understandable later etc. In math-related scientific articles you have whole paragraphs of context around the equation with single-letter variables; in programming if you use a single letter variable, it's either temporary (usually an iterator), or comes from amath equation, everything else is one or max two actual words. Comments are usually short and to the point. Basically, good code is one that you can understand at a glance. (Sometimes it isn't possible, but usually is).
@@kiwikemist Yeah, that other guy explained it pretty well.
I was specifically thinking of complex inheritance trees that require you to navigate 10 different files to understand what's going on.
Let me decide my needs please and thank you -especially if I am learning on my own.
Leave it to Reddit to leave the OP without an answer to his question... So what if Typescript is a hurdle to them...?!
*They can't learn it as they are now and you may not be able to change that about them.
*They can do an open source project without learning Typescript and they will appreciate it more when they do.
*Who is to say their contribution won't be valid? It's not like it needs to even be applied to the project.
*The devs are not expected to even read the pull requests. If they want public contributions this is their problem. -If they want to be charitable and not hide their source, we will all flourish.
Here is my hot-take: Everything should be open-source.
P.S. I love you Prime. I think you are incredibly good natured.
i have contriputed to 1 open source project. and the reason was that we were using that at work, and it had a issue with 1 of the features that we needed. So i fixed the issue and created pull request, it got accepted and we could continue on working :D
I hear so many seniors telling beginner devs to do OSS, but none of these seniors did OSS when they were starting out...
It's definitely not a requirement for a job, I've been developing professionally for over a decade without doing any OSS, including top tech companies in the bay area - and most of my coworkers also never contributed. It's actually hard to find the time when working a demanding job
How empathetic Prime is to new people; people starting their career 'later' in life, people with imposter syndrome, and people just trying to make a living whilst staying passionate about finding joy in what you do is why youre one of the most likeable faces in the programming world.
So what I'm hearing is that if an open source project is mostly used by non-programmers, it's doomed
Which is obviously not true
I mean, look at Blender? Doesn't seem that doomed. Krita neither. Even a little Aseprite, when the author decided to drop GPL, got forked under Godot's main dev name, then gained an actual maintainer and I think it has two people working on it now as LibreSprite.
In Krita I guess not being related to webdev probably saves us from being drowned during hacktoberfest. In fact I didn't even know about it, especially as a problem. There are only some spam proposals to GSOC every now and then.
I hate when people have these generalized hot takes, and then you listen to the take and it only applies to a very specific subset of people. Quit tweeting this clickbait and then justifying it with 1000 qualifiers
Why would people quit doing that if that's what gets them the attention
*GLORY!!!I'm favoured, $255k every 3weeks! I can now afford anything and also support God's work and the church.*
congratulations!!
I will love to be your friend dear as well. as sharing some ideas which you're benefiting.
As a beginner, it's essential for you to have a mentor to keep you accountable. I'm guided by Angelia Marie a widely known crypto consultant.
Thanks to Angelia m Brown
I'm surprised that this name is being mentioned here, I stumbled upon one of his clients testimonies on CNBC news last week....
No doubt she's very good, I started with 5k and cashed out 40k after 1 weeks. I still wonder how she got her analysis
IMO, the way to start OSS is to start by making some cool project you can use yourself. After that you will start seeing problems in other codebases, and may customise them using wrappers, or contribute the solution to bug fixes. This will help you learn and spent time building a good community, and helping people in their problems. This is the true spirit of Open Source.
Is it an old record? Because how could his hair unblue themselves?
When Prime recorded this, the original video was released by Theo 1 day ago. He probably didn't want to release it right after Theo as to not syphon views from the original creator on TH-cam (in this case Theo).
But yes, I'm chanting "always blue, always blue" as we speak.
Refusing to learn Typescript when you're doing web dev and want to contribute to open-source is kinda dumb, in the face of so many projects using it. There's a difference between that and just not liking it and wanting to contribute to non-typescript projects if you can.
agreed. it can also be a mark of laziness - a lot of lazy developers refuse to learn typescript or even some basic jsdoc and end up writing garbage code with 10x more bugs than there would have been if it was typescript. debugging the code is much more difficult because you have to do all the work of the compiler in your own head just to figure out what some variable is - because one lazy developer couldn't be bothered to use a serious language. at this point you should be using typescript or you should be somewhere else. we need to stop with these plain javascript libraries and packages
Typescript has a learning curve. AFAICT OP was just trying to jump into a project they were already qualified to work on given the language familiarity they already have. There are plenty of projects out there that aren't typescript based. The issue is someone tricked this person into believing this is the only way to get a job. Its not
As a undergrad in India, it has already fucked around as a thing to do get a job, as much that I was rushing to learn React to contribute something, but my understanding and use of oss has been extensive(i use neovim btw)therefore I respect the maintainers and devs who do it, and will be lucky+compentent enought to contribute something around neovim, vim or editor space someday, to give back to the community.
It is simply too rough out there. So many people lured into getting CS degrees because they were "in demand" only to find an industry with pretty freaking high barriers to entry. In this very competitive environment career starters search for things that will make them stand out in order to get a few crumbs from employers. First it was getting good at leetcode, then it was having a portfolio, now it is having contributed to open source. A combination of the industry's need for novelty and the bar for entry-level ability is creating this phenomena.
One specific type of "just make something" that was useful for me was to write a suite of very simple tests, one for each aspect of the language, library, framework etc that you don't fully understand.
I did this about a decade ago when i was brushing up on JavaScript for a new job. I found it was a much better way to internalize things like rules for semicolon insertion or non-strict equality, or the semantic difference between let and var, or function hoisting vs var hoisting (in a function).
Reading documentation for a language feature or API is not going to stick if you don't use it. So write a quick test program. And then the jump to using it in an actual project is much more manageable.
"Don't contribute to open source. Your code is garbage, people will laugh and you will abandon coding, and we don't want that now, do we?"
35:48 - 36:04 Hm... when I have enough from programming I help out at the farm up the street with whatever needs to be done... and when my body is sore from that I go back to programming. I kinda feel like those are nice escapes from each other, but both are exhausting and draining in their own way. It's just nice to switch between the types of pain sometimes.
Lol, a few months ago, Theo told us that contribution to open source is the only way to get a job in current market 😅
idk how I ended up on programmer YT, but it's interesting to see the overlap between music creation and programming. Like so often I hear people say "what genre should I make?" "what program should I use?" "what should my effects order be?" and it's so subjective, so case-dependant, and so knowledge dependant that I just tell people that it doesn't matter. Try a bunch of effects, make some shitty songs, grab ten different music programs and see which comes more naturally to you.
Build, see what fails, ask people on HOW you could fix the problem, and try again. The knowledge of what goes where and when will come eventually over time
Prior to a newly permanent sabbatical, I was a senior staff engineer at [global Silicon Valley headquartered company redacted]. Not once did I ever commit code anywhere outside of work. Not once. Even though I was really good at it, I actually didn't enjoy writing code. But I do like money a whole bunch and I can tell you that golden handcuffs are in fact real.
I build a mouse auto scroller to keep my laptop from going to sleep while I'm at work. My cousin made fun of me, cuz "Those already exist". Yeah, my goal wasn't the mouse auto scroller, it was the coding experience of building a tool I already know exists.
> promises its not a clickbait blanket statement "Don't contribute to OSS"
> proceeds to explain well akshually if you are beginner in the Typescript and think you MUST contribute...
The issue with the Typescript thing is that you should choose projects to contribute to based on the project, not based on the language of the project.
If you need to filter out projects because they're in an unfamiliar language, and no projects come naturally to you, then you're just not in the state to be working on OS projects.
Some really good takes here. I've been told many times not to re-invent the wheel. There is a time and place for this though and if you are gaining knowledge by reinventing the wheel it totally provides value. In production environments maybe look at existing solutions before reinventing the wheel. If it doesn't fit the bill, it doesn't fit.
I'v mentored more then one programmer, for free, mostly because it was a rewarding activity and I got more then one good friend out of it. However I no longer do it , cause 1) I don't have as much time anymore and 2) just really hard to find motivated people anymore. I guess problem is that up starts are now spoiled with the enourmouse ammount of free information and resources available and if you don't spoonfeed them they go read another tutorial instead of doing the work and asking questions.
I can speak on this from the other side and I can give you some insights. When I first started programming I was mentored by a wide range of people and they were experienced developers but everybody was new to this little game called Minecraft in 2011.
We were all motivated to make mods for Minecraft and all of us had time enough to talk and help people coming into the modding scene after.
I think the reason why your programming or trying to learn programming can extend that motivation to keep learning it or keep teaching it an extreme amount.
I was learning how to program by creating mods for a game that we were all playing so when I would ask a question about programming to one of the clearly senior modders and programmers it never felt like the tedious nonsense instead it was just helping a modder out try to create something cool
#2 was my initial thought as well. As the years have gone by, there's been less and less interest in _receiving_ mentorship. Instead, too many programmers just want you to tell them what to do. Forget about the how or the why or anything that's important. Just tell them what to do so they can go fail at doing it, then come back to you saying it's impossible, after which you end up having to do it for them. There's no value to these individuals. And yet they still manage to find a way to get a job.
I think the issue here is less the devs themselves and more their teachers and mentors who told them that contributing to open source was De Way.
If you are a new dev and want to work with Web Tech and:
1) want a job - learn TS over JS
2) want to be productive - learn TS over JS
Svelte don’t use TS as maintainers but recommend it for users.
I highly doubt Dr Disrespect here works in a Dynamic language all day. He’s just an anti-TS zealot to the point he is jumping through unnecessary JS docs hoops to reenforce his bias.
TS sucks, though. Can't fault people for trying alternatives. And stop getting offended because somebody doesn't like your programming language of choice. And then you're calling him a zealot. 🤦♂️
@@HyperionStudiosDEpeople should absolutely *also* try alternatives. I am offended on behalf of new devs that will absorb this misguided anti-TS fringe rhetoric from a trusted source and cause them more pain long term. Can’t you see I’m doing this for humanity!
Hacktoberfest can only work if project owners pick a list of contributors that considerably increased project value. "At least 4 PRs" is a broken metric.
14:15 "Tha is incredible ToXiC" - that Hair 😂
Of all your videos this has to be my favorite one as someone who almost got hired i was really hard on myself all i needed to do was build awesome stuff and see what comes out of it.
I wanted to learn TypeScript for a while now, cause I hate JS for not having types. But I only use JS on side projects at home and never at work, so I've never been quite motivated to learn Typescript. But you'r're 4 second Typescript tutorial help a lot! I'm an expert now.
The man was cooking and by 3 minutes the man cooked.
Jeebus, these 9-to-5er career guys are taking the cake. How glad I am that I don't have one of these "Jobs"
Mentorship? Just start coding. Make things. It’ll suck at first. The. You’ll figure some things out. The. You try some other ways to do things and it’ll suck again. And suddenly you can make whatever you want, kinda. And these days, you can use AI to help when you’re stuck. Especially for beginner stuff, it’ll most likely be able to help
“If you ask that question (what oss should I contribute to) you’re not ready” couldn’t have phrased it better.
i think the problem is the job market requires credentials that are so overinflated that "open source" is just being used as brownie points to get ahead
The typing discussion is INSANE. Casting exists in statically typed languages. It's very logical and obvious, even if it has a steep learning curve. Dynamically typed languages are great for learning programming and simplify development but at some point you should be thinking about variables/objects as their types and statically typed languages have the training wheels welded on.
I think it's an overall bad take. If you're a beginner trying to get experience working on a team, and the response is "get a job", *that's* putting the cart before the horse. It's like answering "How do I achieve this goal?" with "Maybe you should already have achieved the goal before you try to achieve the goal." It's not *wrong*, but it is extremely unhelpful to somebody who's actually looking to learn. But then, making hot takes isn't about helping other people learn, is it?
This reminds me of, "You shouldn't do nice things because people will praise you. You should do them because your nice". In my opinion... who cares why someone does something if it's a win-win in the end anyway.
This is what I needed to hear back when I graduated in 2019. I struggled with finding a project that i can understand to contribute which me question my abilities and feeling quite inferior.
That @t3dotgg video is pure gold. In fact, inexperienced devs should never be making pull requests of any type to OS projects. They should be learning and testing things out. That's it!
I have an open source project with tons of Java code and some web UI code for it. Some dude came to me and said: I want to contribute! He redesigned web UI (honestly it was better than mine), but he didn't bother fully testing it. I asked him once to fix things, asked another time. On 3rd attempt I said to him: if you think I will continue spending my time testing your changes over and over, then I don't need these changes. And he disappeared, never tried to fix his pull request ever again.
I don't know what was on his mind. My initial thoughts were he is just a student and didn't work on real projects yet. Now I think he may be the guy who was forced to "contribute to open source"
Here's the take you're looking for optimum primus:
1: You either contribute to open source projects for yourself because you're proud of your ability to help the world OR
2: You contribute to open source projects to help awesome developers and get an opportunity to make friends with them
That's it. If you can find some way to use either endpoint for some other thing, that's up to you. But all OSS offers is bragging rights and friendship points as a proximal goal, and if you don't try to do either of those things as your proximal goal, you won't get anything good out of it.
It's all in the cathedral and the bazaar, by eric s raymond.
The last time I fixed a bug in open source code the company I worked for wouldn't let me share the fix "to maintain a competitive advantage"
I should go find that again, it's been a few years now.
As someone who hires people... junior and senior... open source work helps show me the person's skills. Even though I am the author and maintainer of several OSS projects that has nothing really to do with my interest in others' work. It is just an avenue for me to determine skill. So too would be references, coding tests, etc. The difference for me is that references and coding tests don't really tell me you know what you're doing day to day. If you are helping build, test, package, deploy, write docs, etc. on an OSS project that shows me the depth of your experience. If you can share that information in other ways... great.
The absolute best way you can contribute to OSS is by reporting issues and doing so as detailed as you can
i have seen people steering others away from using a FOSS library because of some edge case, wondered why such an edge case was not fixed as it could have been done with a single check and found the reason was simply no one posted an issue, just defaulted to complaining about it on twitter.
Do contribute to Open Source if your company is using some open source project, and had to fix some bugs in it, implemented additional functionality that can be generalised beyond your specific use case, etc. Do not contribute to Open Source if you simply want to add that line to your CV. Just as simple as that. In other words - contribute only the changes you use yourself and proven them to be necessary in at least your specific use case.
Once upon a time about a decade ago when looking to change career paths to programming after dropping out of grad school, thought about contributing to OSS to have something for my resume. Always hated trite little projects, felt OSS would be far closer to actually working in the industry on a big and complex project. Ended up finding a job without ever contributing to OSS, but it's hard to tell people trying to get into the industry that doing trite projects has the same value as contributing to a real codebase. Not sure if it's still the case, but know when I looked into it back then some OSS projects specifically earmarked certain bugs as beginner friendly. This video made a good case, but it's also hard to discourage it if they're really going to put solid months of contributing and not just hoping for a 2-3 PRs merged and magically landing a job.
This reminds me about the class I had that failed me for not getting 100 points on stackoverflow.
In a mobile dev class, where all questions I had had been answered, or were easily found.
Only guys that got it spammed stupid questions.