That’s the setup. What’s the punchline?
We're a place where coders share, stay up-to-date and grow their careers.
That’s the setup. What’s the punchline?
Paul Isaris -
Sagar Barapatre -
Lucia Cerchie -
Madza -
Discussion (108)
1 developer and a 3.4 Gb
node_modulesfolder.I feel personally attacked
This hurts 😔
Why? Do you nedd only 2.1GB?
It's not the size it's how you use I.T that counts.
ahhahha genius 🥳🤣
None. That's a hardware problem. ((Old punchline to this joke. Haha.))
I also like:
None. The light bulb works fine on the system in my office.
both of these are hilarious
Mad chuckle
Oldie, but a goodie
We can't know how many resources we need until we:
The End.
Tl;dr
Me neither. Hope it's ok. 🤣
I was making a joke about the joke. Lol so jokes on you, I suppose.
That tends to happen from time to time. 😅 It's hard making a buck as a dev standup these days. I was attempting, poorly.
Your name proves you have the upper hand this time, Mr Witt.
This is painfully true.
That sounds more like: How many product owners...
You could have done
npm install -g punchlineand make the whole world laugh at onceYou could have done it in CSS Alvaro while eating Italian tapas.
Wait, what?
Was referencing/joking about the paella food tweet & your daily CSS experiments in one. Supposed to be abstract humor but it was a terrible attempt. Sorry. 😳
I can guarantee that's a thing without looking it up.
I couldn't help it, I looked it up, it's not a thing. I will give it 5 mins and I'm sure somebody will have take it.
This needs to be a thing. CLI of random "dad jokes" maybe??
EDIT: Made it a thing - npmjs.com/package/@vip3rousmango/p...
It's not a CLI, but this has dad jokes galore!
Punchline is a dad joke AI trained from said cli?
Features:
I think we have a product here?
Dear god, Jeremy. I'm ... speachless.
npmjs.com/package/punchline
punchline
0.1.1 • Public • Published 4 years ago
It's a thing.
Curse my inability to use a keyboard. I wonder what it does.
Not surprisingly;
punchlineis an actual package: npmjs.com/package/punchlineWhat dev has time to screw in their own lightbulbs? Just use AWS CloudBulb--abstracts away all the details and they've got a free tier!
Too bad their pricing model is nearly impossible to comprehend. You can't just buy the lightbulb, you have to individually purchase the glass and choose its shape, thickness, opacity. Then you need to pick your filament (from among 17 different shape variations, each in a number of different lengths), decide what kind of screw cap you need (I didn't even know there was more than one option!), and estimate the cost-per-minute given the expected wattage load and service up-time.
But once you've got all that figured out, you'll never need to worry about lightbulbs again! At least until the requirements change...
It's changed since you posted this.
Bulbs, sockets & houses are now a sealed single unit & not user serviceable. To change your bulb please upgrade to our latest house range.
We have houses in succulent pink, lavish lavender, boundless blue & chartreuse. Two sizes.
3 months of free smart door (then $9.99.99 pm). bOS compatible only.
Windows not included.
If you do opt for the optional Windows you will also receive a load of bloatware and occasionally and unexpectedly the house will somehow crash.
~stab~ right at the hear there Tom. :D
Don't you dare make this my next most popular comment.
Sometimes I actually post info. 😳
One to actually screw the lightbulb and 30 to say that they could've done it better.
Hahaha reminds me of this from Toggle that talks about it.
Throwing more devs at it won't solve it faster.
Ah, the mythical man-bulb
I'm here for this
👀🤣
Ticket Closed:
wont-fixReason:
This is a feature, not a bug. I like to work in the darkI don't know but you gotta make a JIRA ticket for it first
🤣 I laughed so hard at this because it reminded of one of my old company where this got out of hand. We replied with "Please send me the JIRA ticket" so often, our colleagues would wonder if they needed to file one to ask us to go for lunch. I could totally see this happening there if someone needed a lightbulb fixed.
Oh, I just wrote a
change_lighbulb.shscript to do it for me...Two. One to do it incorrectly and another to shove them out of the way with
!importantand put it in, before people realize three weeks later it's the wrong lightbulb and it's too late to fix it.Depends on the bulb:
Enterprise bulbs: need 5 developers with 15+ years of experience screwing bulbs.
Startup bulbs: need one developer on 5 redbulls to overengineer the bulb fitting so that it accepts any bulb!
1 C dev or
1 C++ dev and 1 tester or
2 Ruby TDD devs and 1 DevOps guy or
3 frontend Js devs and 2 backend devs or
10 enterprise Java devs and a department of architects
Yeah, all that team indeed.
And the microwave oven will stop functioning. Blame the C guy
If it is an enterprise lightbulb 2 teams of 5 developers working for six months. The requirements didn't specify what color the light was supposed to be so it wasted a few iterations. Also all the unit tests passed each deploy but no one wrote any integration tests to verify if it could ever be unscrewed.
If it is a marketing lightbulb couple hours but if there is any bugs it will require replacing the bulb and enclosure totally.
. lightbulb {transform:rotate(45deg)}
This punchline is the proof that I suck in CSS ...
Brilliant!
:startOne, but at the first try, it will only light up half as bright. Then he'll re do it in a week's time and it will be bright but take two clicks to turn on. Finally another week later he'll manage to do it properly but by this point they will have already ordered fancier lights and he'll have to get started on them.goto:start
so it will be ready in less than a week? We have a client meeting
1)Product manager - To decide do we need to screw or not
2) project managing people - To select the best among the only one option available :P
3) Architect - To design how to screw
4) Manager - To monitor to you and report status back to others
5) Engineer - To actually screw
6) TestEngineer - To test it
7) Finance guy - to pay you
8) HR Guy - To manager all of the above
9) CTO - To manager across all products
10) CEO - to monitor all of you and to gain some insights
PS: Didn't add hierarchy in each level. If added it will reach 24.
:P
One. If turning it off and on again doesn't work then it's the manufacturers problem and someone else should call them to have it looked at.
At least 2, but you're going to need a really large lightbulb.
Segmentation fault
Yeah, but Michael & I already paid off key industry influencers & speakers to rep for us.
Also, we have already been working on bulb.py a python bulb scraper which is an enterprise product & where the real money is.
1 architect to justify their job by making it overly complicated.
2 senior developers to argue how to make the light bulb immutable
1 junior developer to paint the light bulb to look like it's on so the customer can see progress
None - its a hardware problem
one => sudo rm -rf /light-bulbs
Oh, a bulb off.
10/10
Really? You went for an electric wire and a tungsten filament? Jeez, who did this, it's rubbish!
I'm going throw in a POC using google's wif to protobulb with lightstorm capacity. It can provide light for a city, but we can use it on 1 until we need more light.
I'll quickly change the existing bulb and leave it running just in case, but we should be able to kill it within a week.
Back in the nineties it used to take a whole team to do this but now that we know what we're doing I can do it in a weekend no problem. I try to stay humble though, disruption can be hard for non-tech people.
maxcdn.bootstrapcdn.com/screwjs/83...
"This XML file does not appear to have any style information associated with it. The document tree is shown below."
Yep. Working perfectly. 😁
None its the new Dark standard
What is the use case? Team X already solved it, why are we re-inventing it?
Has no one mentioned pyjokes?
It has the title joke with the already mentioned punchline plus tons of other good ones (shortcut to actual jokes below)
Https://github.com/pyjokes/pyjokes...
If it's an entreprise lightbulb, I'm gonna hire 10 developers who have a whole elaborate process for screwing in a lightbulb. It'll be done in ~6 months!
The more developers, the longer it will take.
None. This is a hardware problem. :)
Zero. The documentation was so poor, no developer was willing to fix the problem.
The number of developers you can feed with 2 Pizzas.
Html is how to GET a head in programming. Bdum cha
None. That's a hardware problem.
One. Starts to automate the process. Screws in all the lightbulbs in the world.
5.
1 to actually screw it in, and 4 to argue about what kind of hammer to do it with.
jQuery
Meh, new BulbScript frameworks come out every day
01
the client wants a blue lightbulb that emits green light
None, we all use Dark Mode
Scrum master says no more than 9
0