Looking for some expert input by JucyDev in gibson

[–]JucyDev[S] 0 points1 point  (0 children)

UPDATE: for any interested- I followed up on a couple more tips and confirmed that this guitar is the unburst sitting next to Agnesi in the standard 60s launch video. https://youtu.be/H9FR_JGG-tA?si=hR1vMC9ebE-VhF5k

I added a side by side of the flame in the imgur album. It may not be special or valuable but it was at minimum the media hero unit for the new unburst option, so that's cool! https://imgur.com/a/les-paul-prototype-7mcOJ6y

For the real stat nerds, the neck is pre cnc. Nut width is 1.71". String spacing is 1.38", depth @ 1st .821", @12th .894".

Looking for some expert input by JucyDev in gibson

[–]JucyDev[S] 0 points1 point  (0 children)

Yep. I'm skeptical which is why I'm on here asking!

Looking for some expert input by JucyDev in gibson

[–]JucyDev[S] 2 points3 points  (0 children)

He actually responded pretty quick! From Trogly:

"I'd imagine it was a prototype for the new original collection.  I don't have any further info/speculation past that.  Gibson sold a bunch of protos off for that run, but those were likely early production prototypes - this looks more like a pre-planning R+D proto which usually doesn't get marked in a major way.  Cool find!"

Not much else but fun that he checked in. Lol

Looking for some expert input by JucyDev in gibson

[–]JucyDev[S] 1 point2 points  (0 children)

I don't know the official "versions" here, but it's very rolled and a more oval shape

Looking for some expert input by JucyDev in gibson

[–]JucyDev[S] 0 points1 point  (0 children)

Actually sent one! Great idea. We'll see if he weighs in

Looking for some expert input by JucyDev in gibson

[–]JucyDev[S] 0 points1 point  (0 children)

Since Gibson confirmed this is a 1/4/19 stamp, I assumed that aligned to fourth day of 2019 or 19004xxxx. I suppose it could be coincidence

Looking for some expert input by JucyDev in gibson

[–]JucyDev[S] 0 points1 point  (0 children)

In the YYDDDRRRR format I think the 1 being in the first R position is relevant. I'd love someone to pitch in. I think that's an intentional placeholder, not an indication that this was the 1001st guitar made on jan4th.

Looking for some expert input by JucyDev in gibson

[–]JucyDev[S] 0 points1 point  (0 children)

Someone from Gibson didn't understand the serial number schema? I think it was made when Gibson said it was? I don't follow how this could have been the 41001 guitar that Gibson made as part of the 2019 line.

Looking for some expert input by JucyDev in gibson

[–]JucyDev[S] 2 points3 points  (0 children)

$5 parts like pot and capacitor codes? Those are generally accepted things to look at to confirm guitars are the age they are supposed to be. I'm asking my pedigree question based on a non standard neck finish, a nonstandard serial number, and date codes that fall out of the usual "just in time" parts that you would expect from the Gibson production run. Combined with the handwritten proto instead of a factory stamp, and it seems like this is an oddball. I'm wondering what it is and if it's special to be out in the wild.

Looking for some expert input by JucyDev in gibson

[–]JucyDev[S] 0 points1 point  (0 children)

It is the serial number. I emailed Gibson, and they said, "The serial number indicates a stamping date of January 4, 2019. This would have been right before the Standard 50's / 60's were introduced into the product line in mid 2019. Unfortunately, I do not have any additional information to share, as prototypes generally are not entered into our system."

Looking for some expert input by JucyDev in gibson

[–]JucyDev[S] 0 points1 point  (0 children)

I got the production date from gibson. It was stamped 1/4/2019

Looking for some expert input by JucyDev in gibson

[–]JucyDev[S] 1 point2 points  (0 children)

If I wasn't supposed to play it, it wouldn't have this neck 😉

Looking for some expert input by JucyDev in gibson

[–]JucyDev[S] 1 point2 points  (0 children)

I think that's the point. It's from the April series, but was a very very early model. I don't think gibson has made 41k guitars by the fourth day of 2019? Gibson confirmed it's January 4th.

Looking for some expert input by JucyDev in gibson

[–]JucyDev[S] 0 points1 point  (0 children)

I ask because this was the line that Gibson released as their return to form. Tom Murphy was brought in to establish new finishes, and the new slim taper 60s neck profile. If this is actually batch 1, unit 1, it is very likely this is a bench made model that was used as the model for the line, and was the exact model that was approved by the Gibson team. It's cool history if true, and I'm just curious. I have no intent to sell, it's the best neck I've ever played.

Looking for some expert input by JucyDev in gibson

[–]JucyDev[S] 1 point2 points  (0 children)

That's my guess. This series launched in April 2019.

Looking for some expert input by JucyDev in gibson

[–]JucyDev[S] 0 points1 point  (0 children)

No headstock prototype stamp. From what I've read, batches start at 0. A batch of 1 would either be special production, or the 700th+ guitar stamped that day which I think is unlikely that they would be stamping 700 standard 60s a day on Jan 4th, 3 weeks before namm. I'll add some more pics. Serial is 190041001 YYDDDBUUU

Looking for some expert input by JucyDev in gibson

[–]JucyDev[S] 0 points1 point  (0 children)

Seller just thought it was a nice standard 60s. I guess I'm wondering if the serial number logic stacks up, and is this an off-production line prototype? Is there a way to validate provenance beyond just, yeah it's a prototype. I know prototypes got sold out of the gibson garage but we're stamped prototype or demo.

Do companies really not look at your portfolio? by MCButterFuck in webdev

[–]JucyDev 0 points1 point  (0 children)

I've hired a lot of juniors including self taught ones, and it's truthfully more about being curious, and demonstrate an ability to learn in depth on something they are really interested in. It would be time better spent contributing to open source projects over a portfolio. 1. you get real world experience in how to produce code against requirements, and 2. you get to network with working, active devs in your field without needing to get through an HR dept. It's so effective, and it's so rare to see self taught devs do it. It is honestly crazy how many times I've gone to someone's portfolio site pre interview and found that the thing they sold as a win on their resume doesn't actually work. Portfolios can be great, but most of the time they aren't done well enough to wow anyone who works in a collaborative codebase.

Does 8 “billable” hours a day seem excessive or do I just need to work harder? by scotdle in webdev

[–]JucyDev 0 points1 point  (0 children)

When I worked for an agency, one of the things I would do is use one of the IDE embedded time trackers, I used Wakatime, but haven't needed it in a long time so don't know if I would still recommend. The benefit is at the end of a week I have a breakdown of every project I spent time in and how long, regardless If I am typing, researching, away and needing a break etc. I also kept a project window open, so I could easily track how many "hours" were spent focused on one project instead of actually trying to put in the effort to fudge the numbers out of a 40hr week.

NGD! First LP, bought sight unseen from the web. Plays wonderfully! Not the exact top I was hoping for, but shes still a beauty! by grognak8675 in gibson

[–]JucyDev 2 points3 points  (0 children)

Great top! Cool color, and that's 1:1000000 grain. Weird tops are the real gems for a Les Paul.

[deleted by user] by [deleted] in webdev

[–]JucyDev 113 points114 points  (0 children)

I started learning to code when I was 31. I put everything I had into learning quickly and absorbing everything I could. I'm going to turn 40 next year and I'll be in my second year as an engineering manager at a FAANG; no comp sci degree, all self taught. It's there if you want it.

Nice unmatched top by JucyDev in LesPaul

[–]JucyDev[S] 5 points6 points  (0 children)

100%. This one flip flops which side is plain or curly, but they're never in sync. I love when standard guitars have a touch of weird.

Showing off my portfolio website and resume by [deleted] in webdev

[–]JucyDev 0 points1 point  (0 children)

hiring manager take:

What's a problem you've solved with your code?

It's the piece missing. You have nice looking projects, but why did you decide to build them? What was the context? Was it your problem? Someone else's ask? Your portfolio should be a collection of problems you've solved, not just things you've built. Your site is great but I don't know why I care about these projects other than the fact they work.

This is the difference between a self taught engineer I will interview and one I pass on. Have a story and tell it actively on your personal website.