is it ethical to use third party libraries and other stuff in my portfolio website?

Comments

• CodeMonkey@programming.dev ⁨1⁩ ⁨year⁩ ago

  Yes, you should use third party tools (just don’t take credit for them, maybe even credit the tools used in the footer). In a real job, you would leverage third party libraries to work more efficiently, so you should do the same when showing off your skills.

  source

  • jonne@infosec.pub ⁨1⁩ ⁨year⁩ ago

    Yep, someone that insists on writing everything from scratch is sort of a red flag to me. Web development is mostly about knowing how to use third party packages and building on top of that.

    source

    • intelati@programming.dev ⁨1⁩ ⁨year⁩ ago

      Insists != for practice.

      I’ve been mulling a “reverse engineer” for practice. But yeah, for the portfolio, you want to use the same ethos as you would use in the job

      source
• nwithan8@kbin.social ⁨1⁩ ⁨year⁩ ago

  Absolutely fine.

  Could you imagine if every developer recreated the wheel for every project?

  source

  • colonial@lemmy.world ⁨1⁩ ⁨year⁩ ago

    Oh boy, do I have some C++ codebases I wish I could show you.

    source

    • otl@lemmy.sdf.org ⁨1⁩ ⁨year⁩ ago

      Ah come on, what’s a little spaghetti code between friends ;)

      source
  • ipkpjersi@programming.dev ⁨1⁩ ⁨year⁩ ago

    There are definitely companies like that out there lol, legacy tech can be horrifying.

    source
  • amio@kbin.social ⁨1⁩ ⁨year⁩ ago

    Absolutely could! I've worked in a shop where that was the norm. It was not... fun.

    source
  • Deely@programming.dev ⁨1⁩ ⁨year⁩ ago

    Machine codes, yes.

    source
• BeefPiano@lemmy.world ⁨1⁩ ⁨year⁩ ago

  Please tell me you’re not reusing an existing web server to host your site! Employers want to see that you can handle server programming. Obviously this would be hosted on an operating system of your own design, which is handy because you need to design the CPU too. Don’t forget to smelt your own copper for the wiring!

  source

  • TempestTiger@programming.dev ⁨1⁩ ⁨year⁩ ago

    Dude you joke, but I wanna’ do that someday. Down to the fuckin’ smelting.

    source
  • theherk@lemmy.world ⁨1⁩ ⁨year⁩ ago

    Imagine how impressive yet fully weird that person would be. Like the second coming of Terry Davis.

    source
• lolcatnip@reddthat.com ⁨1⁩ ⁨year⁩ ago

  It’s only ethical if you build the server yourself from materials found in nature.

  source

  • collegefurtrader@discuss.tchncs.de ⁨1⁩ ⁨year⁩ ago

    To program from scratch you must first create the universe

    source
• MrTHXcertified@lemmy.sdf.org ⁨1⁩ ⁨year⁩ ago

  All of society is built upon the foundation laid by others. As long as you’re not misleading people into thinking you created something you didn’t, I don’t see any problem.

  source
• TehPers@beehaw.org ⁨1⁩ ⁨year⁩ ago

  Naturally the answers to your question depend on who is looking at the website, but from my experience…

  Does the ideology of ‘using other people’s tools to create a better product’ apply here in this context

  Yes.

  or would it be considered plagiarism?

  Absolutely not. It’s showing that you can incorporate the works of others to build something great rather than spend time reinventing the wheel. Nobody’s going to look at your website’s source (assuming you link to it somewhere), see a bunch of .ts or .jsx files, and think “oh this person invented Typescript/React/whatever”.

  Should you need to reinvent Javascript, your browser, your OS, etc…? Probably not, and as long as you’re using something built by others to build your website (vscode, node.js, etc), there’s no reason to feel like using a library would be the same. Also, for most real world projects, you’ll be using libraries you didn’t write. This is just showing that you know how to use them.

  Where it would be unacceptable is if you claimed to have created those libraries/tools yourself.

  source
• amio@kbin.social ⁨1⁩ ⁨year⁩ ago

  Yes, of course. Just make sure you're abiding by their license, that'll tell anyone who cares how it may and may not be used.

  source
• aebrer@kbin.social ⁨1⁩ ⁨year⁩ ago

  You could have an "about this website" section that lists the tools and packages you used, and so on. If I saw that on a candidates website (a little section detailing how the page was made and crediting sources) I'd be insanely impressed. That's the kind of person you know you can work alongside.

  source
• chickenf622@sh.itjust.works ⁨1⁩ ⁨year⁩ ago

  Everyone has good answers but I would check the license of more obscure libraries to just be sure you’re not violating it. GitHub has a handy feature that explains the license (if one exists) in easy to understand terms. I’ve never ran into this issue myself but it’s a good habit to have. Especially when you’re working for a company.

  source

  • Spectacle8011@lemmy.comfysnug.space ⁨1⁩ ⁨year⁩ ago

    This is good advice. For example, here’s a tricky one: github.com/IanLunn/Hover/blob/master/license.txt

    Hover.css is made available under a free personal/open source or paid commercial licenses depending on your requirements.

    Would you need to pay Ian Lunn Design to incorporate the library into your portfolio website? It’s used for a commercial purpose technically, but you’re not selling the website to a client. This is a source-available free software license, rather than a free software license. A free software license permits you to use the software for anything, with the only obligations usually being around keeping copyright notices intact and licensing your code in a certain way.

    Generally, free software licenses are simpler and you’ll usually be fine so long as you keep your code available under the same terms. Of course, things get a bit tricky when combining incompatible free software licenses…

    Compatibility is important if you want to combine software with two different licenses into one major work.

    Generally speaking, most software on Github tends to be licensed under a few free software licenses, which are interoperable with each other:

    • MIT License
    • GPL, LGPL, and AGPL Licenses, which have one major difference in obligations between them
    • ISC License
    • Apache 2.0 License
    • Mozilla 2.0 Public License

    However, when you combine MIT and GPL together, you may be obligated to distribute any changes you make to the MIT-licensed portion, depending on how strongly it’s associated with the GPL portion. This is because the GPL is copyleft—that is, it requires you to provide anyone you transmit the binary form of the software to the associated sources if they ask for them. The MIT license does not require this obligation.

    None of this really matters for a website, though, because you’re not transmitting the software; you are instead providing a service. Do keep an eye out for the AGPL, because this one applies even with server-side software interacting with clients.

    I think writefreesoftware does a good job of explaining licensing for developers in simpler terms than the GNU Project: writefreesoftware.org/learn/licenses/

    Sorry for the length…it’s kind of a complex topic.

    source

    • chickenf622@sh.itjust.works ⁨1⁩ ⁨year⁩ ago

      It’s getting into the realm of law where the answer is almost always “it depends”

      source
  • theherk@lemmy.world ⁨1⁩ ⁨year⁩ ago

    Thank goodness. I was concerned reading all the answers. It is this simple. Software has licenses.

    source
• Akavire@kbin.social ⁨1⁩ ⁨year⁩ ago

  Absolutely not considered plaigarism - If i built a website using React + Material UI, that shows im capable using common industry tools. That also demonstrates (to an extent) familiarity with vanilla JS and CSS.

  source
• Diplomjodler@feddit.de ⁨1⁩ ⁨year⁩ ago

  Do i have to resort to coding my portfolio website with pure css and js to demonstrate my credibility and experience as a candidate employee?

  If you did that, I’d think you’re an idiot. Using libraries is standard practice.

  source

  • aebrer@kbin.social ⁨1⁩ ⁨year⁩ ago

    Unless it's like a super minimalist web 1.0 vibe, like basically almost pure html barebones text.

    source
• Paradox@lemdro.id ⁨1⁩ ⁨year⁩ ago

  Would you use them when building things for a client? If yes, then yes. No one gets mad at a carpenter for buying nails.

  source
• tinkeringidiot@lemmy.world ⁨1⁩ ⁨year⁩ ago

  As a hiring manager, I’m always interested in seeing a candidate’s exercise of their skills. But “from absolute scratch” is not something we really do in the working world if we can possibly avoid it, so I wouldn’t expect it in your portfolio. If you’ve got some amazing JS or CSS to show off, definitely do so, but point it out because I’m otherwise expecting frameworks.

  Ethically there are no problems with libraries and frameworks. If you’re using them consistently with the creators’ licenses, we’ll, that’s what those things exist for.

  source
• kitonthenet@kbin.social ⁨1⁩ ⁨year⁩ ago

  Everyone else uses website builders for their static websites, I don't see why I wouldn't. On the job I would expect you not to reinvent the wheel if you don't have to

  source
• ipkpjersi@programming.dev ⁨1⁩ ⁨year⁩ ago

  Of course. It also shows that you know how to make use of third party libraries, which a lot of employers like to see.

  source

  • coloredgrayscale@programming.dev ⁨1⁩ ⁨year⁩ ago

    but then why would they ask candidates to write functions like binary tree traversal from scratch during interviews? /s

    source