jacobyoder

Typoes.

Or 'Zip code'.

It's ZIP code.

Annoys the heck out of me...

When my wife first moved here to the US (from overseas), we'd pass by some used car places and they had cars with big "$1999" and "$2799" in the windows. "Wow... they've got great prices!" she said. I burst her bubble with "that's just 'downpayment'". Eventually we went up close to one to show her "yep, the car is actually $11k, but they put $1999 in giant numbers to get you to pull in.

She's not dumb by any means, but I don't think this was legal in the UK where she came from. That was a bit of an eye-opener for me.

doesn't the 'company' itself also pay taxes on the income?

For most solo folks in the US, the revenue flows directly to you. You could set up a more complex corporate structure to hold the income that you don't pay to yourself, but that corporation would itself have to pay taxes on the income too. I suspect there's not any real savings/benefit until there's enough 'leftover' money to start getting creative/flexible.

Why attribute to normal/boring/commodity tools that which can be attributed to "LLMS" and "AI" and "CHATGPT"?

I just ran the same emperor prompt, and got back a non-black emperor image. He's... slightly Mediterranean, which is what I'd expect, but has an odd nose that doesn't really fit the rest of the face shape/size.

"everyone should learn everything"

I've been in a couple places where I did know 'everything', or... near enough. The more I got to learn outside my own specific dept, the more cynical and frustrated I became (usually). You start to notice that entire groups of people are often just sitting around for days doing absolutely nothing because they're waiting for one person who's out for the week, etc. Or you learn that people just spent 4 months working on something that was rejected in a meeting 4 months earlier, but... the original team still wanted to do it anyway, and therefore couldn't help your group over the past 4 months.

This was legislation passed under Trump, but didn't take effect until 2022.

Take credit for "lowering taxes"... push the effects of the time bomb on to a future administration. Definition of stable genius... ;)

Exactly. How we've thought about what 'profit' is has changed.

When I bought a laptop for my business, it was amortized over... 3 years I think. Kinda nuts but, whatever. It's a couple thousand dollars.

But the example above (somewhere) with the 5 employees at $200k/each... only being able to deduct $100k of that, even assuming $1m in revenue... meaning 'profit' of $900k.... it's just crazy.

No more than 10% in the first year is deductible.

> Nobody says you need to install hundreds of packages.

If I need one, I have to get that package's dependencies. People don't choose to say "Damn, I'd really love to have 1800 dependencies!" But if you have 4-5, you automatically get dozens or hundreds out of your control.

Yes, could you build everything yourself by hand? Sure. That's a hard sell to many depts/projects. "This will take 3 weeks to build" vs "This will take 4 minutes to npm install". That 4 minutes is introducing a lot of potential risk and headache and time later, but it's providing immediate relief.

FWIW, "dependency management" is a problem in every platform, but I have nowhere near the same number of issues in the composer/php world (nor previously in the maven/java world) as I do in the npm/js world.

You've increased the places where things can go wrong (in third party client apps) while not having any control over their quality. We'd hear "oh, IRS opened things up!", then deal with a dozen half-baked clients, and conclude "IRS sucks at something so simple!".

Agreed - public API first is the wrong place to start.

...and Intuit knows a thing or two about "half-baked solutions". ;)

> Get your taxes done with me for free instead of HR Block charging you a couple hundreds"

He had 4 years to do that and it never even came up. To the degree that he's an opportunist, and doesn't hold stock in Intuit, he might support it (or at least not oppose it).

Absolutist takes like this never achieve much.

Yes, it could be better. But an mvp-type launch that does some things well, without trying to achieve everything on day one, would definitely not be a "complete waste". If successful, it's laying the base for the next iterations of functionality.

For a lot of folks, they have one or two W2 forms to enter, and that's it. It's really not that hard. If even a million or so folks get benefit from it to start with, that's great, and we should then build on that.

> Whenever people say stuff like this I can't help but wonder what on earth kind of projects they work on. Even GPT4, while useful for things like reformatting or generating boilerplate code and stuff like that, it's still a far cry from any decent dev I've ever worked with, especially if you're not using a popular language like JS or Python.

I mean this not overly sarcastically, but ... have you seen https://thedailywtf.com ? Between my own experiences, and that of some colleagues, I could probably put together at least a half-a-dozen WTF stories that would rival some of the best that site has to offer. There's enough really incompetent people in positions they shouldn't be in to the point that chatgpt - at this point - could realistically provide better output than more than a few of them.

I didn't think i failed to explain the concept?

I guess I sort of understand a bit of downvoting but... didn't expect that much.

Whatever... happy holidays everyone all the same! :)

And yet... not trying (and often failing) will pretty much guarantee no success at all. It's a tough nut to crack.

Wasn't sure if by 'on the box' you meant the PHP book cover (meaning, you learned PHP) or your site did whatever you set out to do. :)

Look past the embarrassment - if this poster gets just a handful of people to register for "shipfast" service, it's well worth the time it took to build and promote this. Those people will likely buy other stuff from the OP as well.

Loads of people on HN could likely build something 'better' by some metric, but of those, how many would still have the nerve to post it in public? I'm not sure I would. Although I've got something I'm planning to post to show HN sometime soon, my default mode is telling me not to post - someone might post something negative, and I'll be embarrassed!

FWIW, the OP isn't sharing the code, and you wouldn't have needed to show your original 1999 PHP code; just share the built service with folks. That's all most folks care about - the utility/value.

That said, there's nothing (yet?) compelling about this service that I've not seen done before. But it might be new/novel to some.

The code will only run on some specific soviet-era hardware, and the last hardware was destroyed 20 years ago. There's some new regime that is rumored to have rebuilt the original hardware, and is now on the hunt for the missing source code that is framed above the great grandchild of the original developer, who was executed for treason. The new bad guys are gunning for the source code, and it has to be protected at all costs, to prevent a takeover of the world.

I'm already seeing the inheritance jokes write themselves.

Someone have chatgpt write the screenplay now.

They're more concerned with selling flash and giving demos and selling something that doesn't work as expected vs taking the proper amount of time to train the models with up to date info?

Perhaps it illustrates they have people giving demos that don't actually understand or notice obvious discrepancies? This doesn't inspire confidence.

Yes, this feature's only been 'out' for 3 weeks, but obviously the resharper team knew about it ahead of time and had a definition of the feature to develop against. Are we saying the AI can only be trained on 'released' stuff, but other tooling can work against upcoming specs?

I left a company years ago because I didn't feel I was a good fit for the team/project - skills/goals/etc. But wasn't allowed to leave because it would hurt the image of the team to be seen to have people leaving it for other teams. But... apparently, leaving the company altogether doesn't affect the image (and yes... I've left the team, and people internally knew why, so... how does it really save face?)

That too - but keeping the items that deal with the code with the code seems simplest for most use cases.

> We need more well rounded people that also fundamentally understand how their code is executing on the backend so performance and cost can be optimized.

There's also some sort of balance that needs to be struck. As a 'web developer'... to be 'well balanced', I need to understand (or dig in to) the minutia of:

* JS build tools, syntax, oddities, versions, and be able to troubleshoot these in a variety of environment (works locally with these architectures, and runs on production, but the CI pipeline changed to accommodate someone else and now I have to unstuck all this).

* SQL - I need to understand the implications and nuance of various indexing strategies because... hey, PG 14 changed and now our caching approach needs tuning. Should I be using b-tree indices, or something else? Should my indices be clustered? How do I manage replication and backups? And I need to understand the tradeoffs of ORMs vs hand-rolled, vs stored procedures, time-series databases, performance impact of views and materialization. And security.

* Application level - I need to understand various aspects of security at the application layer, and balance security vs usability vs accessibility vs performance vs feedback from various program/product managers and end users. Oh, and I need to be able to troubleshoot the application in a variety of contexts. Oh... and mobile. I need to be conversant and 'well rounded' in various flavors of mobile development (hybrid vs native vs whatever).

* System updates - what? I'm still on JDK 11? WTF? Why aren't you on the current versions? We need to update pronto, because there's too many security issues we'll get dinged on!

* UI - I need to be a CSS master, and if I'm not already on the tailwind bandwagon, I risk losing my job. Or... at least, I'll fall behind as I try to incorporate the new tailwind UI work the new person did because they couldn't be bothered to learn bootstrap 5. And... accessibility - need to be an expert in that.

* Deployment - hey, I now need to be able to understand multiple deployment approaches and processes, be fluent in docker/k8s and various tools, be able to troubleshoot these self-sufficiently. Doesn't matter if these are necessarily the right tools for the situation - someone else dictated this and lobbying for anything else means you're afraid to learn new things.

And... I should be cheery and helpful and positive about all of this being my responsibility. Because when I ask for folks from another team to help, I get told I need to 'own' the project, and I can't just 'throw it over the wall' and expect someone else to do something for me. If I push back on anything, I risk getting labelled "old" and "a dinosaur" and "afraid of change" and "unwilling to learn new things".

tldr - if you actually have teams of people with related yet diverse skills, consider letting each play to their strengths, help support them in their strengths, and organize around everyone doing what they're best at. The 'well rounded' thing has its limits.

That's my point though, was that there are still folks who assume "support" for everything (paying/non) is just "going to be good" ("because it's google/ms/etc - they have a reputation! they wouldn't want to jeopardize it!"). I realize I'm talking about a small number of folks, but even after these folks have been in the industry 10-15 years, their ... naivete(?) - is surprising.

And... I'm not even generally surprised when I get no support on paid for services. Indeed, I'm generally shocked when I get good and timely support from a paid service. Now... that's less shocking when it's "small startup X"; we've all seen small companies get big/acquired and the very thing that got them there - good service/support - is what is thrown out to start squeezing out profits. Staff get overworked, pissed off, leave, quality plummets, people move to the next small startup service, and it starts over again.

"but it will surprise no one to learn I never heard anything back"

(surprisingly?) ... I have colleagues that, even in 2023, will express genuine (not sarcastic shock) when a megacorp doesn't reply or provide decent support. I've only got a few, but the refrain will be something like "wow, I'm kinda surprised google's cloud support doesn't get back to us - sometimes for days. they've always had such a good reputation for support... i hope this is a blip".

It's as if they've only ever read marketing/sales leaflets, then really are genuinely surprised when things are 'normal' (meaning poor performance, non-responsive support, bad/wrong documentation, broken SDKs, data loss, etc).

I've been in open office plans where wearing earbuds/headphones was seen as hostile/negative towards others. This was many years ago, but... not that many (in the mid 2000s).

> Firefox is definitely on par with Chrome these days,

The GP is likely going to be triggered by those words, because... I've seen this repeated every X months/years... "Oh... yeah, you had problems in the past, but it's so much better now"... and... it rarely is. GP will just need to try out again at their own schedule and make their own determination.

I had this standard issue with desktop/laptop linux for years... "xyx doesn't work well"... "Oh yeah, it's so much better now - no problems now". Try the new recommendation - still broken.

I had a f2f with someone at a local meetup, and we got in to "xyz is subpar/broken on linux" (some gnome thing possibly). This happened to be a linux user group, and someone challenged me with "no, you're wrong, it's fine now". So... I pulled out the laptop and fired it up and showed the irritation/bug. The response - after showing that what I was saying was a bug - was a shrug and "Oh, I don't care about that - doesn't affect me". The verbal equivalent of "WONTFIX". In person.

tldr: telling people who've been burned - often for years - that things are "better now" is generally not all the productive. Most of the time, people who have specific/legit issues will figure out if/when they're fixed or tolerable enough.