by marjipan200 on 7/15/23, 1:31 PM with 181 comments
by carlossouza on 7/15/23, 2:14 PM
A better education path (in a bootcamp, university, book, youtube, whatever) would start with the fundamentals and build it from the ground up... not the other way around.
(I just realized how lucky I am for being taught in the best possible order, from the ground up... first the basics... and how so many people didn't have this opportunity)
by zeroonetwothree on 7/15/23, 2:02 PM
Also I find the colour scheme hard to read but maybe it’s just me.
by evandale on 7/15/23, 2:26 PM
I even wrote my own simple test framework that shoves the results on the bottom of a page. After adding a few features I decided to switch it to Jasmine.
One thing I'm noticing is how often you need npm which I find very annoying. How is a JS library or framework anything more than a single JS file that you have to include in your page? Why is everything npm this and yarn that? Jasmine has standalone install instructions that are easy to find but I can't say the same about Jest.
by JohnFen on 7/15/23, 2:10 PM
> Coding a basic vanilla multi-page application (MPA) saves time in development (goodbye babel/postcss/SSR config) and builds are fast (this site builds in less than 1.2 seconds).
I'd hope that builds would be on the order of a small pile of milliseconds! (or zero: a site like that could just be handcoded, really).
> I'm only using these 2 lines of Javascript to add the current year in the footer copyright tag
This could also be eliminated. At least in the US, there is no legal reason to add a copyright notice at all, and you certainly don't have to add a year. Those requirements were removed years ago.
But, if all you want is the year, why not do that server-side? Or bake it into the html and set up a bit of automation to replace the year with a new one every Jan 1.
by willsmith72 on 7/15/23, 2:21 PM
It's like when remix people talk about progressive enhancement to me. Sure, cool, you can do things differently. But why? If you already know the ins and outs of a framework or tool and are productive with it, use it. I'm never gonna hire someone because of how much they "flexed" with their vanilla site, just like I won't hire someone who flexed with their cool fresh-from-bootcamp react animations.
by bdcravens on 7/15/23, 3:27 PM
Someone forgot to tell these folks:
https://buttercms.com/blog/how-to-create-a-blog-with-react/
https://www.sanity.io/guides/build-your-first-blog-using-rea...
(and many more)
I'm firmly in the camp that React and similar frameworks are overused. However, the point is that there's a large part of our industry that is bought-in (and in many cases, built businesses around) the concept of "React all the things" and it's encouraging to see push back.
by city41 on 7/15/23, 2:16 PM
by password54321 on 7/15/23, 6:34 PM
Not interested in reinventing the wheel (no framework), dealing with lots of boilerplate and over-complication (Next/React) or using multiple UI libraries (Astro). SvelteKit is a fine balance between simple and providing enough functionality that allows me to focus on generating content with minimal friction.
by degun on 7/15/23, 2:12 PM
by tjoff on 7/15/23, 2:08 PM
Proceeds with a distracting animated image of the old portfolio, thought that was funny.
by awestroke on 7/15/23, 2:10 PM
by naillo on 7/15/23, 2:05 PM
by madeofpalk on 7/15/23, 4:20 PM
by microflash on 7/15/23, 9:12 PM
Instead of making sweeping statements about the choice of stack, I appreciate that someone took their time and built something of their own. Congrats. Next thing they should do is an accessibility audit and learn from it.
by WesolyKubeczek on 7/15/23, 3:39 PM
P. S. Needs to be even more garish. Remember the "space pigs" theme of FastTracker II? Man, those were the days.
by laurels-marts on 7/16/23, 8:43 AM
When I started my first Node/Express project I picked pug too but quickly realized it was too removed from vanilla HTML I was seeing in the books/MDN and switched to Handlebars. Immediately discovered that Handlebars didn’t have a built in support for something fairly basic I needed and I either had to roll my own extension to it or look for something else so I ended up switching yet again to EJS and I’m still using it a year later today. EJS is perfect if you want vanilla HTML + vanilla JS.
by imiric on 7/17/23, 4:11 PM
Not really. Doesn't your experience, reflected in your CV and the technical interview, already prove that? A portfolio site is nice to have, particularly if you're a designer and want to showcase your work, but it shouldn't be a requirement for a developer, frontend or otherwise.
by dodslaser on 7/16/23, 12:57 PM
While the paperfuge is cool and may even reach higher RPM/G than some bench top ultracentrifuges, it cannot do so consistently.
Putting "Samples were centrifuged at whatever amount of G:s yours truly could crank out on a hand built paperfuge for a solid 10 minutes" in the materials and methods section doesn't exactly scream reproducible science.
by aczerepinski on 7/15/23, 3:29 PM
Before that I had a Phoenix site and I feel like every time I touched it (months apart) I had to update something.
Not such a big deal at work where monitoring for security vulnerabilities and updating dependencies is paid work that we make time for but I hate that kind of busy work on my own time.
by eimrine on 7/15/23, 2:04 PM
by Alifatisk on 7/15/23, 2:58 PM
by codampa01314 on 7/15/23, 4:45 PM
My concern here is that your website _is_ your portfolio - including how you build it. It's not just the content and long narrative that's going to sell you. This new approach has switched from showing what you can do to telling what you can do.
by ofrzeta on 7/16/23, 5:52 AM
by PhilipRoman on 7/15/23, 2:21 PM
by dieselgate on 7/15/23, 11:17 PM
by antigonemerlin on 7/16/23, 7:30 AM
by revskill on 7/15/23, 2:57 PM
I don't have to use any of Hugo, Jelkyll,..., because i can cook my own SSG toolkit right inside React.
by skeptrune on 7/16/23, 12:44 AM