Catch up on stories from the past week (and beyond) at the Slashdot story archive


Forgot your password?
DEAL: For $25 - Add A Second Phone Number To Your Smartphone for life! Use promo code SLASHDOT25. Also, Slashdot's Facebook page has a chat bot now. Message it for stories and more. Check out the new SourceForge HTML5 Internet speed test! ×

Comment That's wonderful (Score 3, Interesting) 70

I just got my head around Swagger, which has umpteen implementations to choose from, and now tackling GraphQL, which has umpteen implementations to choose from. In the meantime, still learning Javascript2015 and trying to use Seneca for microservices.

And while I'm doing that, I have a legacy PHP app to deal with, a legacy Nodejs app we're trying kill, a new Nodejs app that runs our site. And... documenting/redesigning our data model and architecture.

The biggest problem with GraphQL is that much of the documentation assumes familiarity with one or more of: Relay, React, Hapi, Redux, Sequelize, GraphQL plugins (many) and on and on. And... documentation and examples before 2016 tend to be outdated or not working.

It takes me weeks just to analyze all the options available, and pick something that isn't going to throw a dozen new technologies at the team, some of which might already be abandoned.

So, yeah, JavaScript fatigue.

Comment Re:Reversion to the mean (Score 1) 391

Who are these "they" you are referring to? These all sound like management decisions.

And then there's the issue of legacy code that just grows more fragile over time. Again, that's management's responsibility: "add feature, feature, feature; the sooner the better and we can't afford quality."

Outsourcing isn't going to fix any of it. What it might do is lower maintenance costs so that new development can commence with new (younger, cheaper) developers.

I would agree, though: if you sat around in an IT environment this horrible for more than a few years, then you are too comfortable and probably cynical as well.

Comment Re:Problem Goes Far Beyond That (Score 1) 338

I had your job once, and still do (to a lesser extent). People expect you to "do stuff" and "make it work" even if it is illogical and inconsistent or requires some inference of action based on phase of moon.

Sometimes you have to say "No" in ways that don't sound like "no". It can be tricky, but if you just do as your told without question, you're a cynic. A paid cynic, maybe even a popular one, but still a cynic. And then you can bail when it sinks into the morass of unmaintainability.

Comment Re:AI Snippets... (Score 1) 338

Yes, I helped write one of those. Turns out your average person is a poor data modeler (normalization) and type definer (classes). I don't think functional programming is going to help here, but it might.

What is needed in an analyst is the ability to 1) ask the right questions; 2) find the right answers; 3) identify entities; 4) eliminate repetition; 5) determine containment hierarchy and ownership (strong/weak entities); 6) identify and mitigate error conditions

And that's just a start. Once everything is nailed down analysis-wise, then the coding part is easy.

Comment Re: Don't worry (Score 5, Insightful) 436

The key is to run a business that is profitable enough to pay its workers a wage sufficient to cover food and medical and housing. Otherwise, my tax money does it and those dollars essentially make the business owner a welfare recipient by enabling him to be artificially enriched.

If your business doesn't sell a product people are willing to spend enough for you pay your workers a living wage, then your business should go bankrupt. I'm not paying for your beach house.

Slashdot Top Deals

"There is nothing new under the sun, but there are lots of old things we don't know yet." -Ambrose Bierce