HNHacker News
TopNewBestAskShowJobs

EdgarVerona

695 karma · joined February 9, 2012

submissionscomments
EdgarVerona··on Knockout v3.0.0 released
Ah, that is useful! I never knew about that binding - good to know!

(Though the Frontend guys will complain about another 'logic binding' in their Views... I don't know what I can do about that other than to point out that the benefits are worth having those in the views. Virtual elements or not, these kinds of bindings annoy them. I see it as the price you pay for all of the benefits personally, but I'm a person who can't stand hunting for arbitrary jQuery bindings to figure out why a behavior occurred.)

EdgarVerona··on Knockout v3.0.0 released
It sounds like you're finding faults with things I'm not saying.

First, I wasn't questioning the architectural soundness of Knockout. I think it's very sound, and I like it.

Second, I also agree with you that the DOM is available to the developer - however, if you go about blowing away and re-creating DOM elements that should have bindings on them (for example), you're going to have a bad time. This was something counterintuitive to our Frontend developers. In situations where you want to create or remove DOM elements with Knockout bindings, you really should be using Knockout's bindings (or your own custom Knockout bindings) itself to do it, otherwise you're working pretty hard against the grain. I don't personally see a problem with that - so I agree with you that the DOM is available for change - but that was hard to sell to others. :shrug: maybe I'm just a bad salesman.

EDIT: Ah, I think I can see why you feel this way. I should put the counterpoints I put above in quotes, as they don't actually reflect how I feel. I can see how someone skimming would think I actually believe them to be true. I personally have a very favorable opinion of Knockout. I can, however, see why it's a hard sell for some frontend developers. I can't blame them for feeling that way given their points above, though I would like to believe that I can win them over with my counterpoints to it over time. Whether that actually happens... we'll see.

I could also use some more ammunition in that fight, so if you have good alternatives or approaches that I'm ignorant of, I'd be extremely glad to hear them!

EdgarVerona··on Knockout v3.0.0 released
Having worked with Knockout on a fairly large project, I personally liked it as a normally server-side developer - however, it got mixed reviews from our purely frontend developers.

For me, there are several things I like about Knockout as someone who's not a primarily frontend developer:

1) Obviousness of purpose. The thing I hate the most about frontend development is the lack of visibility into what is actually bound to an object. When I run into UI code that's not using some kind of framework like Knockout, inevitably the UI interactions are typically performed with jQuery bindings, and often they aren't terribly straightforward to find for anyone who didn't initially develop it ("what, you bound a mouseover action to everything that fits '.mouseoverable > li > ul > li > .mousey'?")

2) Clearly defined interaction models. I like creating and populating the ViewModel, and thus having a very clear place in the Javascript where I know the business logic and data for the frontend are going to live. When I create the ViewModel as its own Javascript object, I can define the full contract of what data the application needs and what operations can be done against it in a manner that I can quickly locate and fix up later.

3) Syncing of frontend state with data state. (of course, this is an obvious benefit, but...) I love that, once I've defined these obvious bindings, I can then focus more on my model and less on what is bound to that model. It gives me the ability to separate out my concerns, at least more than a scattering of one-off jQuery bindings would.

Knockout provides an obviousness of binding not only because all interactions between the UI, the user, and the model are supposed to happen through these bindings, but because the bindings are supposed to live on the element being interacted with/displayed itself. This made a huge difference for me, as someone who likes to see an obvious relationship between the view and the underlying logic that's modifying or creating that view. The concept of observable properties also felt natural to me, and I didn't mind taking the time to make rich ViewModel objects that had methods attached to them representing actions, and "ko.computed"s when I had more complex scenarios in which I wanted to watch for (or perform) an update.

However, our frontend guys hated it, and I can understand why they feel that way (though I disagree with them on many of these points, and would like to win them over). For them:

1) "We're moving backwards." It's a dramatically different approach that feels counterintuitive - in fact, for frontend developers who've been told their entire career to never put event handlers on the attributes of an element itself, it feels like a step backward evolutionarily. It feels, to them, like you might as well be going back to "onclick=''" bindings.

2) "More upfront work." It's a more upfront work to create and maintain solid and coherent ViewModel objects, particularly when Knockout provides the tempting - but often fragile - alternative of calling "ko.mapping.fromJSON" or "ko.mapping.fromJS" that will essentially make a dumb ViewModel for you, but will also make everything observable and won't give you any of the benefits of creating your own ViewModel with reasonable business logic, computeds, etc... This not only ends up making the bindings feel messy as they start performing complex logic directly in the binding where a computed or method would do, but it reinforces that bad "onclick=" binding feeling that they hate.

3) "We have to surrender control of the DOM." The real killer for them is that, once the DOM is being managed by Knockout, you essentially have to give your control of the DOM over to Knockout. If you start fiddling with DOM elements with your own custom jQuery handlers instead of through custom (or built in) bindings, Knockout is going to inevitably run over your changes in unexpected ways as it itself modifies the DOM. Asking the frontend developers to make custom bindings is, unfortunately, asking for more work (and less intuitive work) than just making a jQuery binding, and thus it presents itself as a lot of additional code.

4) "The path for mixing 'common' ViewModels with 'page specific' ViewModels is not clear." This is one I still struggle with in trying to help find a clear path for them. Let's say that a page loads with a bunch of sections that are common to every page, and there are also page specific data and operations that need to be loaded. Knockout only lets you bind one ViewModel object to a given set of DOM elements at a time, which makes this difficult. My gut is that, if we were to create these ViewModel objects in such a way that a common "binding" Javascript block of code - run after all ViewModel objects for the page were both created and combined into a single over-arching object - existed, then they could all live together. This solution is fragile, however - that means every binding would need to be bound to some object off of that single ViewModel object, which could be prone to breakage as these models change. Essentially, bindings (or DOM elements with appropriate "with:" bindings to scope out what part of that larger ViewModel you cared about) would have to be created with this larger overall ViewModel in mind. The proposals don't sound great when I talk to people about them, and I can understand their hesitation. (if any of you have good alternatives, I'd love to hear them)

5) "We dislike having 'logic bindings' or 'placeholder bindings'." Frequently, the data for the ViewModel isn't actually loaded yet by the time you need to bind. The way of preventing the bindings that require that data from breaking is to have boundary bindings wrapping them, such as checking if the object is loaded or the data you want isn't null... but now you've got essentially boundary checks sitting in the DOM. They dislike those - understandably - and they dislike "with" bindings as well. It all feels like fluff that they shouldn't have to worry about, and that crowds up the view. This is another one for which I don't have a good response or alternative.

Anyways, Knockout definitely has both good and bad elements to it. I encourage everyone to give it a try. You may love it - as I do - despite its flaws, or you may hate it! But give it a shot, it may be a handy tool for you.

EdgarVerona··on Contractors See Weeks of Work on Health Site
I feel that this integration effort is probably exactly where most of the expense came from. There's more to it, of course, but I can see where that one part was probably the large heap of their troubles.

I was not thinking rationally about this whole issue when it first came up and thus didn't measure my previous experience when I was thinking about the issue, but I actually have worked with healthcare systems integration before. Even with all government inefficiency/management aside (we were a private company), interfacing with healthcare providers is an extremely complicated and painful business.

For instance, there is a HIPAA standard interface protocol for things like Eligibility and Benefits and Claim Submission, and most (though still not all!) health care plans have some sort of system through which you can interface for that information - though often it's hidden behind miles of red tape and fundamentally different implementations for various custom fields, and different interpretations of the meaning of many fields. That alone is painful, and that part is supposed to be "standardized".

I can't even imagine the state of healthcare provider's policy estimation systems, particularly when it comes to interfacing with them. It's speculation on my part, but I imagine that each healthcare provider would likely have to have their estimation systems tied into. I wonder how many even had it exposed in such a way at the start of this project that you could tie into it, and how many of them had a wide variety of custom inputs to take into account in their estimating. Though you are right that perhaps the new law allowed/forced them to simplify this estimation process, in which case each of these providers likely had to modify the ruleset of their ancient systems before the integrators could actually work with it. Yeah, I could see even a simplified ruleset for policy pricing and eligibility as being a major factor in slowing down this process.

I certainly wouldn't have wanted to be a software developer on this project, thinking more about how bureaucratic and inefficient both the government and healthcare providers are. I still feel like, even then, 500 million is a dubious number - and I'd like to see where that money went. (how many people were employed on the project and for what cost, what were they being charged for hardware and datacenter(s), etc...) But as a software engineer, I would certainly not have enjoyed working on such a doomed project regardless of whether the money was as well spent as possible or if it was lining the pockets of those further up the chain.

EdgarVerona··on Contractors See Weeks of Work on Health Site
You have a good point. Now that I've slept on this article, I feel a bit more balanced about it. The sticker shock wore off, and I do feel like many of your points are valid now that I'm feeling more rational about the subject.

I feel like I did underestimate the potential costs of this software. How much, I couldn't say, but thinking about it this morning I realized that they probably had to integrate with the systems of (every|many) major existing healthcare provider in the country to actually make this work as desired. I can see now where that wouldn't be cheap.

Is it 500 million expensive? I'm not sure I'm qualified to make that assessment, and now that the initial shock has worn off I'm feeling okay with that. I'd need to see more data - particularly, the balance sheets for the project - before I could say for certain whether the cost was justified. I'd be interested to see that data, but as it stands I'll settle for chilling out about it unless more information comes out along those lines.

EdgarVerona··on Contractors See Weeks of Work on Health Site
The sad thing is that the site being bad should be really tangential to the politics. I personally would love to see outright socialized healthcare, where everyone was mandatorally enrolled in a government created program. I feel like we'd have the most leverage to bring costs down under a centralized and non-profit system. However, this system being as broken as it is - and costing as much as it has - did nothing to help that cause, even though it should be tangential to it. Very frustrating.
EdgarVerona··on Contractors See Weeks of Work on Health Site
The sad part is that it sounds like they're already being paid to do so - they were quoted as being Federal Contractors.

We really need a public peer review system for technical contracting of government projects. This is getting insane. These schmucks fleeced 500 million from our government (us) for a barely functioning website, and now some snake oil contractors are going to come in to "fix it" and fleece us for even more.

EdgarVerona··on Contractors See Weeks of Work on Health Site
Yeah, after reading that article, I get the very strong feeling that these "federal consultants" are in for a second round of greedy-greedy-grabfest. They're throwing insane sounding numbers out there so that they can justify egregious compensation. Someone needs to call these people out on their bluff, there is no way that this terrible site is even close to the LoC numbers they're throwing out there.

I'm so sick of seeing contractors fleece our government (and by extent, us) by pulling the wool over the eyes of those who don't know any better and making sweetheart arrangements.

EdgarVerona··on Contractors See Weeks of Work on Health Site
This is where my hypothesis comes in. Instead of a database, they're codgening a small class and adding it to their codebase for every registered user, and recompiling the entire site immediately following that operation, blocking requests until the recompilation is complete. This hypothesis neatly explains both the terrible performance and the unimaginable LoC estimation.

:)

EdgarVerona··on Contractors See Weeks of Work on Health Site
I don't see it approaching that even with the lines of code for their existing packages. For instance, this is old and out of date, but you could extrapolate a ballpark estimate out of it... looks like back in 2007 or so JDK was about 6 million LoC (http://cr.openjdk.java.net/~darcy/OpenJdkDevGuide/OpenJdkDev...). Even if it increased tenfold since then, it's barely making a dent in that 500 million LoC number.
EdgarVerona··on Contractors See Weeks of Work on Health Site
Was that specialist in the running for being paid to fix it, and thus was overinflating the estimate so he could get paid a few hundred million to fix it up?

I like the idea of a government healthcare program, I really do. But this website... man, someone lined their pockets on this scam, big time.

EdgarVerona··on Contractors See Weeks of Work on Health Site
Yeah, I'd call total BS on that number, unless they did something absolutely insane... I mean, we're talking "instead of saving user information in the database, we codegen'd a set of classes specifically for each regisered user and save them to our repository" level of insanity. Has there ever been software that's even come close to approaching 500 million lines of code?
EdgarVerona··on You Can't JavaScript Under Pressure
8:11 for me - as it sounds like was the case with others, the majority of that time was searching for how to check for specific types in Javascript.

For the "is this actually a string?" check, for example, I started looking for the existence of the match method on the object, which of course would have failed if they passed some random object with match defined so I cheated a bit. I'd like to see the full breadth of test options people took out there.

EdgarVerona··on You Can't JavaScript Under Pressure
Aye, I did similarly, though for some reason I did >= 0 instead of > -1. I wonder what % of people choose one test approach vs. the other?
EdgarVerona··on Ask HN: what would you do with $750k that you just inherited?
Yeah, having 30k in passive income for the rest of my life would be a DREAM. I don't think I'd retire, but I'd certainly start doling out my skills to nonprofits for significantly reduced pay. I don't think I could live on $30k/year, but even if working for nonprofits only netted me another $20k/year total, I could live on that - and save them a significant amount of cash that they'd have otherwise had to pay.
EdgarVerona··on To my daughter's high school programming teacher
Her suggestions are good, but the vast majority of them are unrealistic in a world where we have 30+ kids in a classroom. We have a problem here, and I feel strongly that the problem is class sizes. Blaming the teacher is akin to a tile falling from a shoddily constructed roof and killing someone, and then blaming the tile for the death.

If this teacher saw what was happening and refused to stop it... sure, blame the teacher in that situation. I'd join you in blaming them. But I can't in good conscience blame a teacher for not noticing bullying inside - or outside - of a classroom with the overloaded nature of our school system. Give teachers a 10:1 - or hell, even a 15:1 - student to teacher ratio if you want the kind of one-on-one support she suggests. That would be a fantastic world, and I would love to see that come to pass.

EdgarVerona··on To my daughter's high school programming teacher
That is a good point as well - beyond the monetary needs is the need to cut out the bullshit that has impeded our school systems. We've got a lot of people lining their pockets at the expense of quality education, and we've got a lot of terrible teaching strategies/ideologies that have hurt education more than it ever helped. Would a private system help that, or would it stratify who has access to education at all? I don't honestly know the answer to that. But something has got to give.
EdgarVerona··on To my daughter's high school programming teacher
> Yes, and that is not going to change unless we privatize education.

Or start paying higher taxes so that public education is given the funding they need to implement these programs.

EdgarVerona··on To my daughter's high school programming teacher
Javascript has HUGE barriers compared to Visual Basic. Picture who you're teaching. These aren't generally kids who know anything about programming. They're kids who have never seen anything even similar to programming before. In fact, the vast majority of them probably don't even want to be there.

So you teach Visual Basic, because it has less "gotchas" than Javascript, it reads more like english, it has less intimidating symbols, it can be made to be strongly typed so that they'll receive feedback at compile time, it comes with a powerful WYSIWYG tool built into the IDE, and it has a vast, VAST suit of powerful first and third party libraries that can make the kids feel like they're performing magic.

Visual Basic gets shit on a lot by people, and perhaps justifiably in the business world - but in the teaching world (especially when you're teaching people who are ignorant of and generally apathetic to the subject matter), there are few languages that compare to it favorably.

EdgarVerona··on To my daughter's high school programming teacher
Yep. If a teacher were offered to have a well known software engineer come into their class, I can promise you they'd jump on it - if for no other reason than that it'd give them a break for an hour in their otherwise insane workdays. That was the biggest hint to me that she never actually said this to the teacher himself. What public school teacher wouldn't take her up on that, ever?
EdgarVerona··on To my daughter's high school programming teacher
Public shaming seems extremely excessive when this teacher is just a symptom of the real problem. The real problem here is that we don't fund schools well enough to reduce the class sizes to the point where her suggestions are reasonable. Her suggests would be great in a world of 10 student classrooms - and that is a world that we CAN MAKE HAPPEN. If we were willing to loosen our wallets.

As it is, in a world of 30-40 (and climbing) students per classroom and 5+ classes a day, a teacher who tried to one-on-one mentor every student they came across would be fired. They wouldn't have the time to actually teach the curriculum of the class, and would quickly find themselves out of a job.

Let's not blame and shame this teacher - that's the equivalent of blaming a brick that falls off the roof of a shoddily-constructed building for killing a bystander. Instead of blaming the contractors who built the roof, let's put the brick on trial.

EdgarVerona··on To my daughter's high school programming teacher
I've got a couple of problems with the tone and where the finger is pointed in this article, though I sympathize with her plight.

1) I feel like attacking the teacher is unfair. There is a much more significant root cause that should be addressed, and the teacher's inability to detect her bullying is merely a symptom of that root cause.

Bullying is terrible - I experienced that myself for alternative reasons in Middle/High School - and indeed, inexcusable. Little kids can be assholes, and I do hope that teachers get better at recognizing when kids are getting picked on... but it's a lot to ask when they're strained with multiple classrooms of students that they have to teach. With classroom sizes getting larger, it becomes a laughable proposal to tell them to "pay attention" or "check in" with individual students. These teachers are dealing with potentially hundreds of students every day.

If you want to attack the real problem, attack the fact that teaching is considered and compensated as a "second class career," and thus causes the best and brightest to avoid it. Attack the low pay that teachers receive, the low respect in their community, and in particular the low budgets for public schools brought about by the continual demand for lower taxes. If schools got the budgets to hire good teachers and (most importantly) give them significantly smaller classroom sizes, they could do the kind of one-on-one mentoring proposed: and that would diminish the core problem significantly.

Let's kill the root of the problem rather than blaming the already stressed out teacher at the tail end of said problem. This is a problem we can FIX as a society, if we can recognize that it's worth putting money into our community to solve the problem. This is a solvable problem, made difficult only by the fact that we refuse to give public school systems the funding that they need to sufficiently address it.

2) Far less important in the grand scheme of things, but I feel like people (including this author) belittle Visual Basic unfairly.

It's a great teaching language, and the simplicity of its syntax is helpful for situations like high school where the majority of students don't even want to be there, much less programming. The author's daughter is enthusiastic, and that's great - I'd be willing to bet that the vast majority of that class had absolutely no interest in being there. It's unfortunate, but true - and teaching a straightforward language can at least make the barrier to entry and the remote chance of getting through to some of these students just a bit less remote.

Yeah, it's not going to be something that she'll likely run into in the real world - well, maybe, depending on the industry - but teaching programming in high school is about attempting to break through the oversized wall that is general student apathy. You want to teach an apathetic kid Objective-C so that they can make iPhone apps? Nope. You need something simple - something that will hopefully be simple enough that they won't feel like they're struggling against it. Is it sad that kids are so apathetic? Sure, but wishing they weren't isn't going to make it better. So you give them a softball intro, and hope they feel empowered enough with it to start actually caring about it. Or for that matter, about something, anything.

This teacher also may have been teaching it because it's all they know. High Schools seldom (ever in the public system in America?) have the budget to hire a Computer Science teacher. This person was probably recruited as the only teacher in a related department who happened to know some kind of programming offhand.

Lastly in the defense of Visual Basic, it provides a vast wealth of easy-to-use, easy-to-install, well-documented libraries that perform what (to lay people) seem to be magic. Not only is it easy to learn, but these libraries can be leveraged to very quickly make programs that feel like they're doing something interesting with minimal resistance or struggling against the tools. Learning how to struggle against tools without giving up IS an important skill - but when you're just trying to start by teaching kids to care AT ALL, it's more important that they feel like they're winning. They can learn how to properly struggle once they've learned that it's worth the effort. When they can throw the use of some advanced libraries together and come up with something fun in a single classroom session, they're more likely to also view programming as fun - and thus hopefully just a LITTLE more likely to actually care about it.

In short, Visual Basic is a gateway drug - and a pretty effective one at that.

Anyways, that's my two cents.

EdgarVerona··on How Much Do Music Artists Earn Online? (2010)
This doesn't actually feel like an unreasonable number. Even a radio station with a small broadcast radius playing your song once could get that many people to hear it per day - I think people may be assuming that the value of a single person listening to a song once is worth more than it actually ought to be.
EdgarVerona··on My hell as a 911 operator
You're proposing subscription-based private emergency services?
EdgarVerona··on Xamarin raises $16 million to help you go mobile
Well, yeah - but enough of that massive thing that it's a pretty impressive test of patience.
EdgarVerona··on Xamarin raises $16 million to help you go mobile
These guys slogged through an incredibly grueling task - porting the entire .NET Framework and C# language - through some really hard times. I'm glad to see that it's paying off for them!
EdgarVerona··on Deny PRISM - Generate a PRISM involvement denial statement for your company
Damn, Angela Lansbury's in on it too. They got everyone in PRISM: http://colingourlay.github.io/deny-prism/?company=Angela+Lan...
EdgarVerona··on After XML, JSON. Then What?
Protocol buffers!
EdgarVerona··on 9-Year-Old Girl Raises $15,000 to Make Video Game
But what if the person isn't a college student yet? Same difference, right? So what if someone in high school who wants to go to college made a similar appeal for funding of tuition? I think we're talking about two sides of the same coin.

Now, if there were another site that was strictly oriented to donations or even micro-loans toward such purposes, this kind of appeal would feel right there. But as it stands, I tend to stand on the side of "this wasn't a valid kickstarter."

EdgarVerona··on 9-Year-Old Girl Raises $15,000 to Make Video Game
I feel like this was a con, and yet I also feel strong social pressure to not share this opinion with my friends and co-workers.

1) Did the 9 year old write any of that appeal? I don't think so. Sure, her mom may have written it with her prompting - but the entire appeal feels too well-constructed to pull at heartstrings. There's something... gimmicky about it, something that makes me feel like the appeal isn't genuine.

2) Was this kickstarter really about making a game? No, she's going to a camp to learn about making games - which is cool in theory, if there actually is a little girl and she actually is going to that camp. But it does also mean that the whole premise of the kickstarter's title is misleading at best.

3) The sudden stretch goal bonuses (where'd all this merch come from?) seemed highly questionable as well, and counter to the goal - if she just needs money to go to some camp, why even HAVE stretch goals? This feels like someone who played the system, creating a false situation to gain profit from people. I wouldn't be surprised if it turns out that there isn't actually a kid at all - that it's not even a parent who got greedy, but someone who just flat-out lied to get a good chunk of change.

A lot of people I know seem to believe it unquestioningly, which makes me wonder whether I'm being paranoid. But my gut tells me that if I heard a story like this while walking down the street, I wouldn't give them a dollar (and I frequently give people on the street asking for money a dollar). Especially if they started pulling out merch in exchange for additional donations.

I also love that this article vilifies people who appropriately point out the skeptical parts of this whole situation. I love a feel-good story as much as anyone else when it's real... but this situation throws up more red flags than a well-bribed soccer referee.

← PreviousPage 6 of 7Next →