frankcaron

What I can’t get my head wrapped around with this whole SaaS death thing: do people think that the vendors themselves aren’t going to get similar gains out of the tech you’re using to vibe your own version? And thus, doesn’t any velocity gain equalize?

I found my own site, as well, and I found that particularly charming.

Recently went back [0] to the open web and feel like this inclusion alone justified that move.

Thanks for sharing. Humble and heart-warming way to end 2025 for an old Internet man.

[0]: https://frankycaron.medium.com/of-an-open-web-rebirth-and-bi...

I love this.

Well down the road of this journey myself:

https://www.frankcaron.com/blog.html

Working on killing a lot of JS, albeit my 10 year old Bootstrap theme still has a bunch that's not really necessary.

Men will conceive complex manual and philosophical workflows and theoretical all-in-one SDKs just go to avoid going to Heroku.

"[1] This blog runs on the cloud but that’s because WordPress is a security nightmare and a cloud VM is the easiest way to sandbox it. Ironic, I know."

Really all that needs to be said. Self-defeating post.

Imo, Github has only been moving further in the right direction lately — and more social features ain't it, chief.

The better value proposition lift from giving folks and teams more free private repos was huge, and the increasingly-prominent integration of Github into enterprise tools is facilitating (if not helping to force) the modernization of enterprise dev outside the software industry.

I've never been a bigger fan of Github, personally. Microsoft seems to be doing the same with Github that it did with Minecraft: amplifying what it does well, fixing what it didn't, and making it more accessible to more folks the way they want to consume it — all while not compromising what made it great to begin with.

Former TouchBistro director of PMM cosigning on this exact approach being useful and used by us at the time.

I'm kind of in love with you after writing this. Thank you for doing what so few product and service companies do: naming a product in a manner that makes it almost instantly-understandable as to what problem it solves.

Wrote this up out of frustration tonight. Would love to hear from other PMs on here about what they've done to effectively scale product at their orgs.

Good eyes! We were there after a con at Rackspace! It was as deadly as you've foretold.

For the record, and for those asking for this to be a real game, FitRPG for iOS is planning to deliver on some of that very notion. It's a super cool app; and I say that with absolutely no affiliation (srs). Google it.

That was technically the literal interpretation. :)

Figures that I submit this for karma myself eons ago but it only now, via another HNer, pops to the top. :)

- The fat MMO guy

That's an interesting thought. I think the missing piece is really the Apple TV playing games, and for whatever reason (maybe storage?), they just can't or don't want to make it happen.

Couldn't agree more. Not launching the game controller or talking up some big new release, like Oceanhorn, whilst teasing the Apple TV gaming could have really put a dent in the somewhat-weak line-ups of gaming systems that are going big this holiday.

What a waste, Apple.

While I use 1Password myself, a few companies I've worked for now have been using Passpack (https://www.passpack.com/en/home/) which provides a neat way to "share" passwords securely in the event that an employee leaves so you don't lose any accounts. This is in addition to AD or Google Apps depending on the company's infra.

I truly look forward to the burst of this flash-in-the-pan game startup IPO bubble, albeit with slight sorrow for the truly hard-working game devs who are feeding the producers and business staff with their undervalued efforts.

HL3 will be a timed Linux-exclusive for Valve's official Steambox. Calling it now.

I was referring to the fact that there aren't as many (or even a handful of significantly noteworthy) incubators in the GTA / Canada at large.

While this is great in theory, it's likely not going to lead to anything other than one marquee Toronto Star story about the foreign entrepreneur who found success in Canada.

Canadian VCs are far too risk averse and conservative; that's why the uptick of start-ups in all areas of the country, even Toronto's own would-be "Valley" of Liberty Village and the Junction, hasn't fielded much in the ways of success.

Until Toronto VCs start taking more risks and going down the road of helping people experiment (much like YComb itself), I don't see this doing much other than acting as a talking point for why Canada is a good place to live.

(I say this as a Torontonian who has worked almost exclusively for start-ups in the GTA and is now moving to San Fran to work for another one).

As a technical writer who has a long history of digging into the code alongside the engineers, let me just say this: good architecture and design docs for software can save a ton of time writing doc as the development ensues and completes.

Whether it's a whiteboarding session or scribbles on a napkin, don't throw anything out or let it go forgotten. Get an internal wiki or use Google docs and save everything! Your tech writer will thank you.

Neat to see how much more traffic HN has been getting over the years and yet how the average age seems to be creeping up. Oldmanysiteis?

"There's an API for that" is the new "there's an app for that".

In my experience, this really and truly depends on the amount of technical debt your organization is willing to take on. I believe the key to cutting corners is to fully and openly acknowledge that you are doing so, and to justify the reasons for it and the short-hand version of how it should be done without limitations to time/cost/quality.

There's been many times in my career where making a drop date or getting a demo working has been vital to the life of the project, product, or business. In those instances, cutting corners and shipping the minimum viably-functional product was done consciously, and we made clear note of how to come back and remedy the temporary design/architecture/implementation.

tl;dr: Do what's right for the project given the time, cost, and quality requirements but document the decisions and justify them.

At this stage in your career, don't quit a job until you can line another job up. That said, if you can line another up that progresses your career, don't hesitate to quit.

As the old saying goes, you have to look out for #1 (you): no one else is going to in the working world.

While I'm all for moving on and up, though, when your career is just beginning, gaps between jobs don't look great, even if you have a good story for why they exist. Thus, don't leave until you have a new place to go.

And remember another age-old saying: "the grass is always greener..."

Awesome idea. Getting devs to track time is always a pain, and this kind of thing is a great way to get the data needed for less-annoying project management.

The tech writer in me is losing his shit over how cool this is.

A fair assessment of the basic OAuth 2.0 impl, but I'm left wondering how to as-simply state the value add for developers to implement an OAuth 2 workflow instead of just relying on SSL.

Is the additional overhead to development worth the gain in security for the straightforward "access my own protected resources" use case?

I really hate the source article's headline; it completely subverts the article's most important point and renders the whole article one that will likely be glossed over by readers who wouldn't otherwise know what Desert Bus is. Something like "How The World's Worst Video Game Makes Sick Kids Happy" would've been a lot more eye-grabbing and useful in highlighting why Desert Bus is so important.

The New Yorker never ceases to disappoint me.

I wonder how Apple will react to @dropbox's new Datastore sync in the long run. Hopefully it won't pull the rug out a la IAP, UDID, OF, ...