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

It works well with reasonable people, but it has some flaws:

- unreasonable people will not doubt themself, but reasonable people will. So this discussion has a tendency to turn in favor of the unreasonable.

- unreasonable persons will make you pay for not being on their side. Coming to them gives them a heads up for doing that.

- you usually have less problems with reasonable people, so if you do have a problem, there is more chance the opposite party is not reasonable, and hence risking point 1 or 2.

So I'd say, "test if the opposite side is reasonable with a smaller grievance first".


This makes it key to have a culture of reasonableness. Like an extended prisoners dilemma, if there are worse penalties for building a reputation for being unreasonable, people will be less likely to take that path.


[flagged]


You are essentially saying the opposite of the article without any real information about what you're basing your decision on (except for apparently a hate of reasonable people and all that you believe they stand for). You're not going to change anyone's mind that way, was that what you were going for?


They're an existence proof of why the reasonable person principle doesn't work in practice.

If you assume this is performative, it's an exploit to control the environment the RPP is in. If it's authentic, then it's a person who cannot bridge the gap to meet the reasonable people, therefore the reasonable people must comply with the demands of the authentic and aggrieved person.

Probably best to assume that for MOST people, operating by a Reasonable Person Principle is best. You've got to account for outliers, though. You can't operate both a reasonable person principle, and total inclusivity, at the same time.


Correct. And the unwritten rule (inside the unwritten rule, lol) about the CMU computer science culture is it's hyper-exclusive.

It's a lot easier to assume reasonableness if there's a giant gate in front labeled Everyone Who Passes Through Here Has Gone Through The Admissions Process... and a giant slide in the back labeled That's A Nice Academic Career You Have, It'd Be A Shame If You Violated The Institution's Code of Conduct

Similarly, the reasonable person principle tends to work in practice on this forum thanks to moderation, votes, and the extremely occasional ban. The parent of the comment you replied to is getting harder and harder to read as the day goes on.


Yeah, that's also part of the "doubt" dichotomy: if you are reasonable, you will ask yourself "am I unreasonable?" while unreasonable people will be certain they are being reasonable.


ublock origin is available on firefox mobile is you use android.


You can, with pyodine: https://github.com/pyodide/pyodide

Here is an example instance: https://notebook.basthon.fr/

The thing is, creating a whole stack in pure JS would be very hard, since the current scientific stacks uses a lot of fortran, assembly and C with python to bind them all. Or julia. It's millions of man hours we are talking about.

So compiling Python into WASM is probably the best deal for such an app.

For the regular web, it would be a deal breaker: you don't want to load 15 mo of runtime before being able to interact with a web page. But for such a scientific app, it's not a problem. Besides, were you to write it entirely in JS, the size would be huge as well.


That's because they are not programmers. One should not expect them to be experts in 2 fields. They do their work with the tool provided, and if we want a better output, we need to provide better tooling or accept what comes out.

I want my physicists to spend their mental effort on physics, not on software architecture.


As a scientist myself, I strongly disagree. If you spend a non-negligible amount of your time telling a computer what to do, you are, indeed, a programmer. And as such you should be expected to become a decently proficient programmer.

Physicists are not mathematicians, and yet they are required to acquire a relatively high degree of proficiency in maths because maths is a fundamental tool in their job, and nobody would argue otherwise.

The attitude of considering programming a mundane craft to be picked up as-you-go is the main reason why the scientific software landscape is such a shitshow.

/rant


As a fellow scientist I wholeheartedly agree! I find that programming skills (and willingness to improve on them) are strongly correlated to success as a (experimental) PhD student, much higher than mathematical abilities. The ability to automate your experiment or do a quick simulation is a huge productivity boost.

However, the programming education in science degrees is absolutely appalling. Just show them how program a newton raphson method in matlab (without any considerations for performance) and expect them to know how to program.


> If you spend a non-negligible amount of your time telling a computer what to do, you are, indeed, a programmer. And as such you should be expected to become a decently proficient programmer.

Just like if you are standing on your two legs most of the day and sprint once in a while, you can be considered a runner. Sure, you can play with semantics, but most people cannot run a marathon.

> The attitude of considering programming a mundane craft to be picked up as-you-go is the main reason why the scientific software landscape is such a shitshow.

Err... That's kinda my point?

> And as such you should be expected to become a decently proficient programmer.

It's very, very hard to be good in 2 different fields. Most people won't have the ability or the context to do so. Even if they did, the time and energy spent to do so would be taken from their main activity, which is why we employ them in the first place.

It's not reasonable to ask a data scientist, geographer, biologist or physicist to follow up with the right practices to deploy the latest sci-stack on a linux server, understand the trade off between GIL locked python thread, asyncio and multiprocessing or spell out what WSGI stands for.

Hell, I know a lot of professional programmers that don't know those things

> Physicists are not mathematicians, and yet they are required to acquire a relatively high degree of proficiency in maths

The quantity of information required to be learned is of one or two orders of magnitude, because the field of maths required to perform physics is quite stable, and well understood.

IT is a very young field, in constant flux. The scientific stack is a moving target, not to even mention the web one. Nobody can expect them to understand python, numpy, pandas, then a web framework, then css, then js, and html, probably some frameworks for them, a builder or two, how to deploy all that stuff in dev, in prod and architectural concerns for linking all that stuff.

That's crazy talk.


I think you are seriously overestimating the "programming proficiency" of many scientists. I don't think the OP meant that scientists should be experts in the web stack or even in the intricate details of the scientific stack. However, I do expect that they should know how to write reasonable maintainable code, i.e. use functions, modules, don't just copy paste code around between cells etc.. (this is seriously the state of much of the scientific programming world).

>The quantity of information required to be learned is of one or two orders of magnitude, because the field of maths required to perform physics is quite stable, and well understood.

Apart from the fact that some areas of physics are really at the forefront of maths, this also ignores the fact that learning the level of proficiency required for graduate work in physics is significantly more involved than learning about some best practices in programming.


If you think functions and modules as an example of what makes a code maintanable, then I'm afraid we won't be able to agree.

I've seen data scientists handling big code bases. The problem was not they couldn't use the language features. The problem is that they would be always lacking essential information for their mission because their is not enough time in a day for a regular human being.

They would put a md5 hashed password in their db, create an xml format to be reusable only to realize they'll need to hard code some value later, or have a gunicorn running to a crawl because they didn't know how to calibrate the number of workers.

It's just too many things to know. Once they mastered that, other things would come to bite them.


> If you think functions and modules as an example of what makes a code maintanable,

It’s definitely a part of it. This isn’t an all or nothing thing, one can learn good practices without encumbering their scientific work.


Shouldn't we just reduce the "data science profession" to what it clearly is then: shuffling around numbers and statistics in excel and python, in the hope of generating a useful insight or two and the occasional whitepaper as you go along?

If you don't understand the tools you're using, or the environment you're in - you're not any more of a "data scientist" than pretty much everybody else. My carpenter is a data scientist going by this logic.


But it is just an assumption. I work as a data scientist for 5+ years and from practical point of view, it is not just data wrangling. It is worth to mention that going through that logic we assume that programmer fully understand how to develop model in production and how to handle it in some border cases, which is not true.


Maybe they are not programmers but they surely work in a team or company where everybody is supposed to work as efficiently as possible together. Simply throwing your unstructured and unreadable code over the wall, with the excuse that it's not your key responsibility so somebody else should fix it, is just bad.

It doesn't mean of course that everybody is supposed to be an expert programmer, but a minimum effort to help your colleague is surely not too much to be asked.


It's not a matter of responsability or will, but of ability. Expecting a fish to fly is a very bad working relationship.


Structuring and documenting your code is not rocket science. It is not expecting a fish to fly, any scientist should easily be able to pick up this skill.


> That's because they are not programmers.

Beginners not being aware of some best practices doesn't automatically make them not-programmers.

I work as a data scientist and I see it as part of software development. It's just a different domain - some people do front-end, some do mobile or embedded, I do data science.


Data scientists are not programmers. They are data scientists.

Just like I'm not a data scientists, I'm a programmer.

Now, I can use pandas in a pinch and makes pretty graphs, but my statistical analysis will never be on part with yours.

Just like a pianist hobbyist will have a hard time to rival somebody who does that 40 hours a week, although he may be able to play a few fantastic pieces.

Hell, even a web dev programmers, if ask to code a GUI desktop app, is not going to do a good job.

IT is becoming a very large field.

And scientists are not even from this field.


As a data scientist I spend more time writing software and building things than I spend doing statistical analysis (and I like it that way). That's why I consider it part of software development. Don't be tripped up by the word "scientist" in the job title (I wrote another comment about this in this thread). Also, it's a very broad field and it varies a lot from company to company - if you've had some interactions with data scientists, don't assume that what they do applies across the industry. I'm basing what I'm writing on having worked at/with companies of different sizes and in different industries.


If you want to play with names and semantics, I'll leave you to it.

That's not my point.


Well, my overall point was that you got the names and semantics wrong.


You essentially say that a web dev and an GUI desktop programmer, are both programmers even though they can't do each others job, but a data scientist who programs all day is not a programmer? That seems like a pretty arbitrary distinction. I would agree with the OP, that data scientists are often essentially programmers they just require a very different skill set than an web dev, but their required skill-set is probably closer to a compiler programmer than the web-dev is.


I agree that they are not programmers but in my opinion it cannot become an explanation to write a code which become non repeatable, especially if they have big impact on how the flow will look on production environment.


Scientists are not meant to create code that ends up on production. Once they have a working concept, they should team up with a programmer to make it live.

Again, if it's not possible, then you accept the imperfection of the result, or provide better tooling.

There is no blame to put on them whatsoever.


> Scientists are not meant to create code that ends up on production.

You might be mixing up the terms. I don't think that the point was about "scientists" in general, it was about "data scientists". The first is a common term used to describe someone who does science in some professional capacity. The second one is a very broad job title within software which very often includes writing code that ends up in production - at some data science roles that might even be your main responsiblity.


Even among devs with very close speciality, the difference in productivity is immense. Take a iOS team, make them dev a MacOS desktop app, and see their output plummet in their of productivity or quality. They will end up doing a good job, but it will take between 6 months and a year to catch up with a specialized team.

A data scientist is not even a somebody trained as a programmer. Their strong suit is data analysis, and it turns out one of the tool to manipulate data today are programming languages so their do it.

But I as a Python trainer, I train data analyst regularly, and they don't have a clue about language ecosystems, how the OS work, data formats or reliable software architecture.

They mainly want to output their graph, pdf report or other media to serve their conclusion. They may want to create some reusable algo, or machine learning model, but that's the limit most of them hit.

If one take their code and put it in prod (which I know happens, don't get me wrong), that's not the data scientist fault. They are doing their job, in which programming is just one of the many means to an end, and is not their specialty.


> But I as a Python trainer, I train data analyst regularly, and they don't have a clue about language ecosystems, how the OS work, data formats or reliable software architecture.

This is like teaching some JavaScript to complete beginners at a bootcamp and then declaring that front-end developers aren't real programmers because they know so little.


Oh no, I train frontend developers, and they know a lot more than data scientists when it's about programming.

I'm not talking about complete beginners. I don't train beginners.


I disagree, many, many scientists hire a professional statistician to do the stats for their papers.

Similarly, they should hire experienced, qualified software engineers to write/check the software in their papers.

They don't because 'everyone can code - its just logic'.


Err... That's kinda my point ?


Mea culpa - I interpreted your comment to mean: only once its ready to go into industrial use.


Maybe there's a confusion here between programming and software development. One is a tool for the other, but can be used by itself too.

I'm a physicist (not "data scientist" though I work with plenty of data), and I've been programming since 1981. Anything I do, I want to do well, especially if I do it regularly or it could cause problems if done badly. I've made an effort throughout my career to keep up with good programming practices. I do that out of a combination of pride, curiosity, and professional ethics.

But I'm not a software developer, meaning that I don't create software for widespread or long term use by others. We have an entire department for that, and many of their techniques are quite specialized.

Naturally it wouldn't surprise me if further improving my skills also moves me closer to being capable of software development, and I'm happy to learn and apply their techniques at a pace that works for me. I think that a scientist who is capable of learning to program should receive guidance on how to do it better, but perhaps in stages, such as:

1. Writing code that has a better chance of working, even as it gets bigger and more complex.

2. Working with others on projects that involve sharing code, meaning that it has to be readable and conform to agreed upon standards.

3. Creating code that can be confidently "shipped" for widespread or long term use.


Nah, data science is an inherently multidisciplinary topic, and most data scientists aren't domain experts in anything. Data science is mostly valuable to the extent that data scientists learn the full spectrum of skills needed to do their jobs well.


Just like devoos, this is a fallacy. Eventually you can't be an expert in everything. Lost devops are very good at either dev or sysadmin, and not too bad at the other. Same for data scientists.


I would call "can only use Jupyter notebooks" very bad at programming, not merely "not too bad". It's well below expectation in my opinion.

Whether you choose to call it "good" or "not too bad", there is a minimum bar of competence that data scientists need to meet in statistics/ML/AI, programming, and their domain of application. And the ability to move from Jupyter notebooks to Python modules/packages is a basic.


The market also leads to food full of fat and sugar. Without strong campaigns against cigarettes, the market would make sure it's everywhere. The market also has no problem showing deeply violent content to children.

At some point, the status quo was slavery, death penalty, child work, women domination and against gays.

Just because if you do nothing the current equilibrium tends in some direction doesn't mean it's the right thing to do.


Of course. I'm not saying the market is right in everything "it decides". On the contrary, I think it's usually wrong in the long run - it shoots past the social optimum as businesses continue to figure out new ways to extract money from established things.

Anyway, my point is just that this may just be market at work, and not some conspiracy or minority exerting undue influence over society.

(And my second point is that, for the same reason, I don't buy the argument that shitty technology is good because that what sells with most people.)


Exactly, when the article used their example of bug found in production, I knew what would happen before the reveal, because it's what always happen.

Damn it, you got a language with namespaces, why do you think that is ?


>Something weird happened over the past decade.

PR happened. The big players have figured out that if they want to keep misbehaving to make money, they needed people to not fight them. To do so, one amazing tool is to make sure the entire way to speak about the topic is controlled by them.

Internet gave us the ability to share more, and we though it would allow us to defend our self better, to make people more aware. But we didn't predict that an entire industry would specialize into creating submarine communication that pretend to be an organic one of such quality that the average human can't tell the difference.

With old school com and ads, you at least knew somebody was trying to sell you crap. Now, you are nicely having a chat in what you think is a community of peers, while being exposed to commercial and political influence that have been crafted to reach you here without raising your BS radar.

And with AI, it's going to get worse.


> And with AI, it's going to get worse.

Cynical prediction: AI influencers, possibly with a hybrid components. Accounts powered by some GPT-esque generator, acting like a real human, shilling various widgets in a naturalistic way. Use humans-in-the-loop to add randomness and natural-ness. Or just AI extending how much marketers can generate.

And/or microinfluencers. Platforms benefitting (otherwise regular) users in some way to adopt some stance. Oh, you said good things about Brawndo, and our fingerprinting was able to trace your social media to your amazon wishlist, which happens to have Brawndo in it? Free pack of brawndo shipped to you from a "mystery admirer". Post a selfie with a logo prominently, CV bots pic it up, get swag. Gossip quickly spreads that if you say nice things about X, or take pics of Y, you get free swag. Suddenly your feed is full of your friends giving a lot of organic-seeming attention to corporate products. It'll put the Sunoco bumper sticker campaign to shame.


Yes, that's what I had in mind, and I suspect it's already going on to some extend with votes and follow ups, which is easier than content generation, until the later becomes so good you can let it roll free.


Politics too. People are far too eager to cede power to these big tech companies just because it will hurt those on the other side of the political spectrum now - without realizing that that power is gone forever. DMCA takedown, demonetization and ad revenue scene, privacy - it's all the same story.


Was (is) there any normal person who was in favor of the DMCA? Geeks knew about it and hated it; non-geeks were unaware or, if informed, hated it. It was a product of lawyers and moneyed "entertainment" industry interests.


I'm suspecting that PR firms have understood for some times now how influential those social networks were to reach people that traditional in-your-face propaganda works ineffectively on. If you want to touch the heart of geeks, artists, activits and passionate people, you need to do it in a format that they will accept, and because they are very active on the world, those are important targets.

For things like HN or imgur, I assume there is a way to pay them to get the com you want in a way that appears to be organic. That's the best way to make money for those kind of sites after all. Want to make a billionaire a hero? Suddenly, comments everywhere say how much the guy is great, links to articles of his achievements raise to the top and critics are down voted, or/ and counter answered elaborately by what has all the signs of a long time user account. Want to sell a new movie or a political program? How about some "fan-made" memes or technical article that everybody seems to love?

Even better for those firms, why pay if you can avoid it? In reddit, work patiently to have a lot of accounts that are mods in topics you care about, and you basically own the system for free. Even better, now others will pay you to do com targeting those communities.

In that sense, I think facebook and twitter are at least more honest about how they influence society because they are explicit about their paid communication offers.


Given the average user don't know what a url is and a pedophile can use the darknet, I'd say criminals are not all dumb.


It is not so easily comparable. It’s all about your intrests and expectations.

Darknet might sound bit complex, but as darknet user, you literally just install different browser.


Something like 40 percent of people use the default browser installed by the os.

We're just in an echo chamber of people who know what JavaScript is, and that distorts our perception of the world.


Can you give source for that number? Regardless, browser is like any other app. If that amount of people don’t know how to install apps on their computers, then we have a either real dump people (or just lack of motivation) or great UX design failure in general.


Users are on average incompetent, not dumb.

It's a dauntins realisation that sinks in once you have to do support for a web site or app catering to the general population instead of a niche.

They don't read, don't know the diff between an app and a web site, don't know right click or drag and drop, think google or chrome is the internet and overall their startegy to solve any problem is as follow:

- look for something obvious that seems like the answer but is not scary

- click

- wait for it

- repeat 3 times until ok or give up and call someone or get angry or both

Working on a streaming video site really opened my eyes on this one. Most tickets we received were insults, some were incomprehensible garbage, a few were actionable request from someone not understanding anything about their computer.

This is nothing like your github ticket. Your parent number are being generous IMO.


Apple seems to have completely botched this PR stunt/feature.

Reading your comment, I realize how these… ‘criminals’ could use phone number networks to share illegal sexual content peer to peer.

In other words, Apple doesn’t need to analyze your images to find these criminals. They only need to analyze the frequency or quantity of flagged images.

In other words not one image correctly/falsely tagged, but individuals and networks of individuals who are *collecting* and *storing* mass quantities of these images. And, they’re using Apple privacy and security to hide from law enforcement.

Racketeering?


Using sqla as a base is such a sane decision. It leverage a rock solid layers with async support and a battle tested ecosystem while offering a versatile query builder when you need to opt out of the ORM paradigme.

I have a huge respect for your work.


Thanks! :D


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

Search: