HN user

lemme_tell_ya

205 karma
Posts0
Comments44
View on HN
No posts found.
jQuery UI 2 years ago

Same (2012 for us)!

The Widget Factory was awesome for its time and not well advertised.

jQuery UI 2 years ago

In 2012, we build the front end of an application by making heavy use of the JQuery UI widget class and extending it for our own needs. That application is still running today largely unchanged on the front-end.

time is possibly too short (especially if you have kids) to learn new things that aren't simple, even if better

Having a kid has drastically altered my ability to learn new things outside of work, simply due to lack of time. I never could have imagined how big of an impact having a kid would be, its crazy!

The worst thing is when you actually manage to carve out some time to do some learning or experimentation with a new tool, library, etc only to find out that it sucks or you just don't have the time to pick up or whatever.

Does annual billing make sense here? This is the sort of service I would only anticipate buying for a few months at most. Either the idea is getting no traction and I move on, or its getting traction so I start building get an MVP and do signups myself. Just a thought. I like the page layout, nice bright and clean.

If this is your product, could you display the SaaSes in a list with a short description?

Having to click on a logo, then dismiss a modal for each one is tedious.

among the 999 most popular crates on crates.io, around 17% contained code that didn't match their code repository.

Wonder if that includes all the crate "squatters", countless times I've found a crate that was empty (and had been for years) because they wanted to reserve the name...

We used 1.6 for a large project in 2014 or so, the 2.x release removed key features for us and we were never able to upgrade. The direction they went after that just never really worked for us so we only have that legacy project still running.

True, though good quality high capacity batteries are likely out of reach for most, and getting them shipped to the Philippines might be a challenge (In my experience things can get shipped and arrive from the US to PH in a couple weeks at most, then they get lost in the abyss for months, in my experience they always arrive, if not months later.)

Also, I do wonder if running on 220V makes the AC side more challenging/expensive, of course if you can run most things off DC this point is moot.

The Philippines has been slow to adopt electric vehicles,

That doesn't surprise me, anyone who has lived there knows how terrible the grid is. Brown-outs are a (frequent) fact of life, entire outages not uncommon. I've seen the Manila Airport lose power on multiple occasions while waiting to get on a flight.

What does surprise me is the slow adoption to solar power, my guess is that the grid isn't prepared for that either, and off-grid setups can be fairly expensive for many that need it most.

It would also be nice if integrations could be blocked or de-authorized from the AWS side

I have no idea how DataDog integration works but if I had to guess I'd expect to setup an IAM account for them to use? If so, you could delete the IAM account they're using.

I think the incentives are different for Netflix and Youtube.

Youtube wants engagement so they can sell you ads, Netflix just wants subscribers, they don't care how much I watch or how engaged I am, just that I keep my subscription.

Oh yeah, been there. I personally find Windows to be a terrible server OS. I'd rather be stuck with a fleet of AIX machines or something equally uncommon (but still nix-ish) than any Windows system.

My first day at my first full-time programming gig, I was asked to look at some reporting job that had been failing to run for months. I logged in, found the error logs, found that it needed a bit more memory assigned to the script (just a tweak in the php.ini) and let the team lead know it should run fine that night. He was shocked, "Dude, if you just fixed that report you probably just got a promotion, no one has been able to figure that out for months." He was joking about the promotion, but my boss was just as shocked. I'd realize later that most the other people on the dev team didn't like linux and wanted to rewrite everything in .NET and move everything to Windows so no one even tried with anything related to any of the linux machines.

I completely agree with you that this is maddening and increasingly common in all walks of life. The situation is not getting better either.

Having worked for companies that do this kind of contract work I can imagine how this could occur:

The state puts out an RFP (Request for Proposal) written by someone completely removed from the technical aspects and actual work to be done.

After a bunch of BS, some company gets awarded the contract and begin work. They quickly find that what was requested in the RFP doesn't make sense and they have to either drift from the exact requirements of the contract, or deliver something completely broken.

Not wanting to lose the customer, or violate the contract they decide to forge ahead, working with the state to form the requirements into some form of sanity. Some stories get added to a sprint by someone who doesn't know what any of it means and they sit...

They sit, maybe even for multiple sprints (because everyone has given up on the burndown chart being even remotely accurate anyway and no one has time for retrospectives) until someone screams loud enough about it.

Then, poor programmer, likely knee deep in several other tasks, gets asked to work on this story, it needs to be done by end of the week and it's Thursday.

They begin implementing the feature, look for requirements about address length and find none.

They have two choices:

A) Stop work, ask the business analyst or whoever might know, they'll ask their counterpart on the state side, who will then make a request to IT, who will be just as swamped and take four days to give them the answer because Monday is a holiday.

B) Set some default that seems reasonable (50?) and move on.

It's easy to see which one they end up choosing here. Besides, there's likely several things to be done, this one field is a tiny part of it.

Because there's no test system for the back-end (maybe it's written by the state or some other state contractor) they mock it in a database and move on.

But lets say they get done, everything moves along nicely, stuff gets deployed. Then, not long after it's been pushed to prod they get a bug report.

The bug report says that addresses are being truncated in their IBM AS/400 (or equally antiquated mainframe.) there is a limit of 31 characters that needs to be enforced.

Lots of screaming from people with project, manager, and business in their titles.

The programmer, now gets assigned a new story for fixing the bug, because they were the only one that worked on it, they can't escape their fate.

It's Thursday again and the only window they have for the update is this Saturday, they have 2 other projects that are due this week...

They put in the validation for 30 chars and push it out to be deployed.

Then the author hits the aforementioned bug. It will likely never be fixed as the poor soul that worked the feature has now moved on to be a sheep farmer in the mountains.