Hacker Newsnew | past | comments | ask | show | jobs | submit | more BiteCode_dev's commentslogin

With the new dev ops crave, we expect people to understand backend dev, and front end dev and design and sysadmin and networking and project management and infra and product ownership. Not to mention be proficient with tools related to those things.

The result is not people getting experts at all those things, but getting capable of producing something with all those things.

Obviously, to do so, people must take shortcut, and container ~= docker ~= "like VMs, but lighter" is good enough as a simplification for producing something.

Now there is something to be said about the value, quality, durability and ethics of what is produced.

But that's a choice companies make.


What space do you take ?


That depends of the scale.

See ansible and the YAML config files.

In this case, a real language would have been a better choice.

Also, sometimes you need to generate config files. In that case, templating is not always a good choice.


Then again, we have Chef (ruby DSL), and from experience I've found that they tend to turn into a mess that very easily can become hard to reason about. Although, I'm not sure if this is because of the design of Chef itself, or just simply because it uses a real language.


Humans have the tendency to think they understand something if they have a label on it. It helps them take decisions faster, whether it's good or bad.

If you tell people you don't know what causes their respiratory illness, they may think you are incompetent, and feel helpless.

If you tell them they have acute bronchitis, suddenly they feel empowered. It just means they have an inflammation of the bronchi. It says nothing of the direct cause, nor the indirect cause: a virus, tobacco, dust, air pollution or asthma. It says nothing about how bad it is. They don't even know really what it implies for their body or their treatment.

But now they think they know.

Call something a democracy, and nobody will check if it is.

Call something a privilege, and people will start to want it, working hard for it.

Models can be used to help your interact with the world. But they are also used to avoid interacting with the world: if you use them as labels, instead of comparing the model with reality, you get a shortcut to take decisions. It becomes a mere name to justify a decision process instead of a tool for the decision process.


I'm not sure I agree.

While technically bronchitis could be any inflammation of the brochial tubes, a diagnosis of bronchitis usually means that that it's the patient's major problem. It'd be odd to describe a cancer as "bronchitis" even if it involved brochi. So you do learn something, in a Griceian sense, from the relatively uninformative diagnosis. There's also the implication that there are some tools for managing it, the doctor's seen it before, etc all of which are reassuring.


"Mind is the great destroyer of reality" - a quote from one of those ancient dusty books. Our mind is a machine that creates models and labels for everything, to avoid dealing with the illigible reality.


>If you tell people you don't know what causes their respiratory illness, they may think you are incompetent, and feel helpless.

Agreed, on the medical front this also leads to a focus on sophisticated diagnostic tools and numbers versus a 'true' cure.

>Call something a democracy, and nobody will check if it is. >Call something a privilege, and people will start to want it, working hard for it.

Let me add one more to the list. Call something a 'right' and people feel denied if they are not given it. Eg. voting rights. Even where one can vote, consent is generally manufactured but people feel empowered when they vote.


"Gun rights" are totally bogus.

Let's enumerate rights: "Life." Okay. "Liberty." Gotcha. "Pursuit of happiness." Yep. "Private property." Might need some asterisks on that one, but sure. "Carry a weapon around in case I might need to murder another human being very quickly." ???

It's been this incredible PR campaign based around the fact that people are illiterate and don't know what "bear arms" means (jargon for "serve in a militia"[1].)

[1] https://languagelog.ldc.upenn.edu/nll/?p=43559


The actual right is to self-defense - itself a derivative of other fundamental rights. Access to effective means of self-defense follows from there, just as abstract freedom of speech has many derivative rights like freedom of the press.


An abstract right to freedom of thought allows for extensive time and place restrictions plus libel laws, etc. The right to self-defense (which I will concede) allows for restrictions on weapon ownership and usage.


Of course it does. But it doesn't allow for arbitrary restrictions - a restriction has to be justified, and not just on the basis that it seems like it might help.

In legal terms, the standard for restrictions on free speech in US is "strict scrutiny" for this exact reason. So while we have time and place regulations, there are also many safeguards in place to ensure that those aren't abused. To give one example, permits can only be required once disruption reaches a certain level (e.g. a solo demonstration on a sidewalk shouldn't need one), and for cases where fees are associated with said permit, it cannot be imposed on somebody unable to pay, or for whom it would be a considerable burden.

I can assure you that the vast majority of proposed gun control legislation would not pass strict scrutiny. This is evident even from the degree to which policies vary in other countries - for example, when it comes to "assault weapons", the definitions vary significantly even in US state laws. Yet there's no obvious correlation with any practical effects if you compare, say, UK (which bans all semi-autos) and Germany (where you can own an AR-15).

The laws that do seem to matter are mostly those regulating the owners directly, and even then it depends a lot on the policy. E.g. universal background checks for each purchase sound rational in theory, but evidence on their effectiveness is lackluster. OTOH a license to possess, that has to be periodically renewed, has a much more profound effect.

Czechia is a particularly interesting case, being very permissive wrt "what" - comparable to US, even with shall-issue concealed carry! - but much more stringent on "who", and this seems to work just as well as UK's tight-fisted approach: https://en.wikipedia.org/wiki/Gun_law_in_the_Czech_Republic#...


Not sure if you were in agreement with me, being sarcastic, or nitpicking.

But the history of comments is certainly not dull. Look at my profile, and see if the link mentioned in it catch your fancy, if it does, shoot me an email.


Medicine is super-bad about not being able to tell a symptom from a disease. A lot of "diseases" are just symptoms with Latin names and a set of empirical remedies.

Psychology in particular seems to have come to the conclusion that if you can name an assortment of 4 out of 10 symptoms, that counts as having identified single disease.

I think part of the problem is that we're so good at applying various techniques that no one bothers to think anymore.


Well historically the symptom /was/ the disease effectively without imaging to meaningfully separate "appeasing the spirits by ritual boiling" vs "killing microbes". To go with a niche mixed metaphor part of the issue is epistemological low resolution. If the extended "senses" and knowledge are lacking everything is imprecise.

One path of medicine closest to that sort of symptom vs disease separation being practical is phage therapy. It could be called true alternative medicine as an actual alternative as opposed to a euphemism for "false or unproven" but is generally less practical in spite of its other virtues. Because a proper phage needs to be selected per target pathogen. As opposed to not caring what strain of virus it is and just treating the symptoms so the patient can recover and not die.


'Medicine' being a stand-in for 'diagnosis'? Because medical research is all about underlying causes these days. Maybe 50 years ago it was just a corpus of traditional cures. But those days are gone.


>If you tell them they have acute bronchitis, suddenly they feel empowered.

In the The Imaginary Invalid (17th century) Molliere makes fun of it. Doctor explains how opium works through its "dormitive virtue."


Stremio and popcorn time. It's netflix for torrent. No popups or animation. I think there is one banner somewhere, but it's so discrete I don't even remember.


Problem is, that's how they get away with everything.

They fix nothing, then wait for somebody to need them enough, or have compassion enough to handle their mess.

Basically here, they are saying: we didn't listen to all those competent people that told us we should have cleaned this system a long time ago because one day it will bite us back. We didn't think technical debt was a thing. It has always worked. And it's virtual. And IT is always exaggerating anyway.

Now it does bite them back, and do they take responsibility ?

No. They ask for competent people to have mercy and save the day because the situation is dire. Because this is special this time, unlike the other times.

This is completely not like with the health care system that never got fixed and now the medical personal is paying for it so that the people don't suffer as much from this mismanagement.

They will not pay more. They will no fix anything. They will not respect you more, change the way things are done, or take any responsibility for this. And in fact they will probably guilt trip you into give up your health to overwork on this with less resources and for less pay because it's an emergency.

A friend of mine works in an hospital right now. She has been at work for 15 days straight. They already told her she won't get paid for the days she was not supposed to work but did.

Then as a final fuck you, if this turns out ok, if the catastrophe is avoided, they will get the reward.

The nurses or the programmers ? They will be forgotten in a week. Nothing will change.

But for the mismanagers, their superior will thank them for managing this situation well. They may even get promoted and have more responsibility.

So you have the choice between saving the money of poor people now and reinforcing the suck of the whole system, of letting people suffer for a chance of a redo and purging the ones that lead to this.

This is a terrible choice to have to make.

Especially since we have the empathy to make us discuss this, while clearly they don't.


This is honestly a terrible take. NJ did try to modernize the benefits system in 2007, awarding the contract to a company that is now owned by HP. News article: https://www.nj.com/politics/2014/11/nj_ends_118_million_cont...

EDIT: surprised at the downvotes. Parent asserted:

> we didn't listen to all those competent people that told us we should have cleaned this system a long time ago because one day it will bite us back.

And the historical record showed that NJ made that realization at least before 2007 (which is when the contract was awarded)


No, it's not. These state IT systems and this habit that leads to their inevitable downfall needs to die.

They respect nothing. Scope? No, we need to fulfill every need and some. Budget? No, of course we don't have cash, and we have to be very careful, it's the taxpayers' money! Time? It's already late! (Yet they weren't able to get it done in 10+ years.)

They have no real competency, they don't even have competency to delegate this to someone competent. And they lack the competency to manage their own inconsistency regarding these issues.

The linked tweet thread is a perfect example of this. (Rampant project mismanagement; too big to fail; they introduced some Hadoop scoring system to match inconsistent records and whatnot instead of simply throwing out all the bad data and handing the rest separately - eg hiring a bunch of unemployed people to go over them.)

A state that should be at the top of any kind of project management and procurement hierarchies wasn't able to supervise an IT system project. It's so incompetent just thinking about it will lead to spontaneous combustion.


Yup. Exactly right. And they think the 26 year old outside consultant knows how to fix the problem better than the 50 year old government programmer, who management has spent 17 years beating down their self respect.


Consistently assigning work to big firms who consistently screw up... All they want to do is show that "they're trying", and the charade will continue until someone does get fired for buying IBN.


I bet NJ wouldn’t accept any excuses from a small business that tried to claim “they’re trying” if they had technical issues with payroll.



Surely outsourced and offshored isn't something to praise them for


Like off-shored protective medical gear, off-shored pharmaceuticals manufacturing, and now a country full of unskilled 20 somethings that can only do phone apps and coffee baristas.

Companies will not like it, consumers will not like it, State budgets will not like it,

But like cobol programmers, we need to learn how to make things and build our own supply chain.

My old employer did not listen last year when I retired. Nobody was assigned to make an annual change to a REXX program. I learned it on my own because it predated me. But the process was so rigorous because we had to be our own RACF Admin to make our own RACF I’d to get to the datasets to change, then run the programs, but they got rid of printers connected to the mainframe and tighter up FTP so much that if took days to refresh passwords and ftp print files to your pc hard drive. Then run programs in C# that scalped off the first column and read the mainframe page skips....

Am I was suppose to teach this to a C# programmer who would not need to run this for 6 more months. I blame management. They loved outside consultants and treated our own programmers like loading dock employees, write ups when 5 minutes late for work.

They wanted me to take a brand new high end pc with me when I retired. I left it on my desk when I left. They had 6 months to learn it.


Given a choice between the government doing it and a company that has been specializing in this type of thing for decades, why wasn’t this the best choice?

It’s not like HP is some unknown foreign company.


> Given a choice between the government doing it and a company that has been specializing in this type of thing for decades, why wasn’t this the best choice?

Because the only thing they are specialized in is sucking tax money from the government.

> It’s not like HP is some unknown foreign company.

That's their only pedigree. In other countries they also took a lot of money and delivered crap. So people should be aware by now. But with all this corr^W lobby ...


Getting Atlas Shrugged vibes. Lots of parallels with this situation actually.


Seems like OP is describing the plight of the average worker who gets left to clean up the mess with no credit at the end of it all and less of the business leaders or executives.


IIRC, the capable workers were the first gone to Galt's Gulch. The story dwells on slightly-less-bad business people running around like decapitated chickens trying to keep things working, but the real heroes just quietly noped out.


> So you have the choice between saving the money of poor people now and reinforcing the suck of the whole system, of letting people suffer for a chance of a redo and purging the ones that lead to this.

What a terribly wrong take. If you really believe the system is that corrupted, and that horrible then you know darn well that the count of people who suffered during this emergency won't make a difference. There will be "accountability" in some form, but it won't be driven by how many people did or didn't get money for food at all.

Whether you help them or not won't change the system. So instead you're saying scores of families should go hungry so you can stay on your high horse and lecture.


That's a good reason. You don't need a moral reason to not choose a paid job. The reason scores of families will go hungry because of the mismanagement, not because one human did not step up to keep the mess rolling. In analogy, the reason Africa is starving is because of the past and present extreme exploitation from foreign powers, and said foreign powers sponsored corruption and violence. Not because "a heartless middle class salary man did not send his monthly 10 dollars", turning a blind eye to the real causes of the situation.


The big corporations, will get $18,000 from every taxpayer from their future tax dollar.

But they struggle just to give each worker in this country $1200.

It is hush money. Then next year they will tell us it is taxable income. Watch.


Yes, don't forget there will also be some deniers calling it a fraud afterwards: https://twitter.com/TheKouk/status/1211123181051768832


Somebody is above the legal department. That person doesn't care that the department is important or not, only that it's useful.

So how does that happen ?


But that also means that:

- the code is not reusable outside of a database setting. So not cacheable.

- the code is not reusable accross different storage layers. So not portable.

- the code may needs updating if the schema change, you can't abstract that

- changing the logic means a db migration

- testing the code requires a DB

- tooling support to check that code si limited to SQL tooling, which is very weak, especially for code completion, refactor and debugging.

That's a lot of constraints for just making the application logic a lot simpler.


the code is not reusable accross different storage layers. So not portable.

In my 23-and-a-bit years of web development I've literally never changed the database engine on a project. Maybe that happens on other people's projects, but it's not something I consider important or even useful really. The notion that you can swap out your database for a different one without changing the application code to take advantage of the db you're moving to is ludicrous. Of course your database code isn't portable.

Websites that used MySQL and Myisam tables with raw SQL statements written as strings in PHP for the first decade of the web is one of the reasons why so many web developers still don't use things like transactions, stored procedures, views, etc. That's a bit of a tragedy. The web would be much better today if everyone had been using Postgres's features from the beginning.


If you write a project, you probably won't change the database. But you may add new data layer services such as a cache backend, a search engine with, a secret server, a session store, a permission micro service, etc. They will all interact with permissions and change where you source the data from.

Then there is the case where you don't write a project, but a lib. Or the case where you extract such a lib from a project. In that case, you limit the use case of your lib to your database. Because if you don't change database during your project life time, the users of your lib may start a new project with a different database.

This is why Django ORM allowed such a vibrant ecosystem: not because it allows changing the data base of one project (although it's nice to have and I used it several times), but also because it allow so called "django pluggable apps" to be database independant.


I have never seen anybody migrate out of PostgreSQL, but I HAVE seen people migrate out of Oracle, and DB2 because they are so expensive its worth the cost to migrate.


  I've literally never changed the database engine on a project
And some of us do it several times a day because we deploy to prod with Postgres but run testing and CI with SQLite.


Me too, until I found how fast Postgres is starting in Docker and for different languages there are now libraries helping you writing tests using Docker containers.


Well, you're doing it wrong. It's easy and fast to run tests against real postgres (takes a fraction of a second to spin up the DB for your tests if you do it right).


I agree, but I also see the benefits from the other side, so I’ll play devil’s advocate:

- it is cached, in the database’s memory, where the cache can be invalidated automatically. It is better to cache views than data anyway.

- it is portable to every platform postgres runs, which in practice means it will run everywhere. Portability between databases is overrated because it rarely happens in practice.

- the access control logic evolves together with the schema, guaranteeing they have an exact correspondence. This is a good thing.

- integration tests should involve a live database

- have you looked at jetbrains datagrip?


> it is cached, in the database’s memory, where the cache can be invalidated automatically. It is better to cache views than data anyway.

The cache may not be for the data in the data base, but for something else (task queue, calculation, user session, pre-rendering, etc). You effectively split your cache into several systems.

> it is portable to every platform postgres runs, which in practice means it will run everywhere. Portability between databases is overrated because it rarely happens in practice.

As I mentioned, for a project it doesn't matter. For a lib it does.

> the access control logic evolves together with the schema, guaranteeing they have an exact correspondence. This is a good thing.

Not always. Your access control logic could be evolving with your model abstraction layer, which frees you to make changes to the underlying implementation without having to change the control logic every time. It's also a good for your unit tests, as they are not linked to something with a side effect.

> integration tests should involve a live database

Integration tests are slow. You can run them as you develop.

> Have you looked at jetbrains datagrip?

It's fantastic. If you are willing to pay the price of it for and force it on your entire team. If you are on an open source project, will your expect that from all your contributors ?

High barrier of entry, with no modularity. Linters, formatters, debuggers, auto-importers, they all depend on that one graphical commercial product that is not integrated with your regular IDE and other tools.

Not to say it's not a good editor if you do write a lot of SQL, as JetBrains products are always worth their price.


The tooling is just fine for me, DataGrip or not: I wrote a ton of PostgreSQL triggers and utility functions in Javascript thanks to the excellent plv8 (free) extension. Development and unit tests for these functions is as easy as plain Javascript.


> Development and unit tests for these functions is as easy as plain Javascript.

Since most popular product in the JS world are product to avoid writing Javascript (webpack+babel, typescript, coffeescript, jsx, etc), and plv8 supports non of that nor does it support standard unit tests framework like Jest, I'm not convinced.

To make things even worst, remote debugging is not supported anymore: https://github.com/plv8/plv8/issues/131#issuecomment-2377111...


I personally this time around, I found no need to even use a framework for unit testing a single javascript function.

If I had to do something that feels too complex, I'd write some interfaces in TypeScript to represent the tuples, then implement the function in TS, and compile it into plain JS in order to deploy it to plv8.


It also means you need a per-user database connection which isn't feasible in many applications as the recommended number of concurrent connections is typically quite low.


Not necessarily. You can SET ROLE at beginning of transaction and DISCARD afterward. This is what postgraphile and postgrest do, for example.


Oh cool, I didn't know that. Good to learn!


postgrest actually does a `SET LOCAL ROLE`(transaction scoped, so no need to DISCARD), but yes, that's the gist of it.


This absolutely isn't required; I think you might be getting confused with RBAC rather than RLS. Handy infosheet: https://learn.graphile.org/docs/PostgreSQL_Row_Level_Securit...


You can just change the user for every query.


Rust management system is first class because the language has been designed from scratch 10 years ago.

Python has been around since 1991. It came out before installing dependencies from internet was a thing. It had support for Windows XP, Atari, Solaris. You gotta be able to pip install stuff that are written in C (numpy) or in Fortran (scipy). It had been implemented in the JVM, .net, and Python itself using pypy.

All those years, what we knew about or needed from packaging system changed, and the tooling followed. We had easy_install, then setuptools, then distutils, then distutils2, the pip + setuptools again. We had virtualenv, then venv.

You cannot break from the past easily, especially on such a popular language, with half of it's user not even being devs.


While you're not wrong that it's much easier to build systems with the advent of foresight, Rust also supported Windows XP, Solaris, stuff in C or Fortran. That's not the issue.

It's really purely the "designed from scratch 10 years ago" (though, only six years for Cargo).


Because conda and other tools don't mix.

If you only use conda, it works.

If you start to pip install or use venv, it will break at some point.


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: