#difference between procedure oriented programming and object oriented programming

[queer-100-days-of-code]

Day 16: Object Oriented Programming (OOP)

Today, I learned how to use Object Oriented Programming (OOP), in python. Up until now, I had been learning something called procedural programming, which is where the code progresses through the main function and keeps variables sequentially. This is one of the earliest ways of writing code. It works really well for things like Fortran. However, once the code gets complex enough, this method can be a bit tangled to read.

With OOP, instead of defining every piece of information as a variable, you can create a lump of information called an "object". For example, rather than having a different variable for each part of a car, you could just have one object, car1, which has all these variables already attached to it and defined. Also, this lets you easily create multiple different iterations of the same type of object, rather than painstakingly define each data set individually.

I was able to retry the coffee machine project again, with OOP in mind, and this setup made the project much easier! :)

(weird cropping so I don't accidentally flash my computer file address) Here is a pic of what the finished coffee simulator comes out with! See you tomorrow! :)

More specifics on OOP under the cut --

Variables contained within an object are split into two types: attributes (what an object HAS, variables) and methods (what an object can DO, defined functions). We call functions within objects 'methods'.

A 'class' is the type of object which is generated. For example, if we generated a bunch of waiters, the class would be 'waiter' and the object would be, for example, 'kevin the waiter'. The class is the "blueprint" of an object.

To define an object, you would use the following syntax:

car = CarBlueprint(speed,gas,color)

where car is the object, CarBlueprint is the class, and speed, gas and color are all variables which can be different between different cars. Note that the first letter of each word in the class is capitalized as a matter of syntax (Pascal-case).

If you want to access a variable or method from a class, use the same structure as with referring to modules: car.speed, car.stop(), etc.

I also learned about a python package called Turtle Graphics, which has a turtle object inside that can be told to paint a line on the screen in a variety of different colors. Part of the lesson today was learning how to read code documentation, so I could figure out how my turtle worked. You can find this module and a TON more on PyPI.org, the python package index, which has lots of useful predefined modules that other people have created for public use.

To install packages from PyPI, in PyCharm: file -> settings -> projectName -> Python Interpreter -> plus sign on the upper left, and then enter the name of whatever package you want in the search bar -> Install Package on the lower left.

[iiasha-archived]

not coding homework technically, but i think you could still point me in the right direction. I do a lot of coding but it's all for data sciency stuff. like i don't know any computer science, or what makes a "good code", and most of the things you complain about are things i've never heard of.... where should i start looking if i want to actually understand how to do things well

ooooo so this can be a bit tricky since data science by nature is actually pretty different from the type of programming i tend to talk about in that the goals are fundamentally different

i kind of googled and skimmed this but i think this article goes over it pretty well, but to offer my own thoughts on it basically data science to me is very research/developmental based and not necessarily meant to be maintained and/or run for a long time. as such it doesn’t have to necessarily be efficient, the focus is more on experimentation and maximizing the different types of results you can get.

production code on the other hand DOES have those intentions; at that point the research is done, we select our best algorithm(s) and we want to maximize efficiency and maintainability so that it can easily be scaled. but of course there’s a happy union between the two if you know where to draw the line.

that being said, a lot of the work i do is take such “data sciency” code and productionize it, which is why i bitch and groan about it all the time lmao (perhaps unfairly afdjklad). so it’d certainly be wonderful for me if the people giving me this code were more conscious of good software practices associated with production code.

but i’m not sure where to point you somewhere specific other than just probably googling “good programming/software practices” hahaha. but these are some points that i think are good starters. things in bold are like “topics” you can probably google easily.

understand, like really understand, what DRY is, and a lot of the techniques that come with it

this stands for “don’t repeat yourself” and there are a bunch of acronyms like this in software design but i consider DRY one of the more important ones and you’ll see it reflected in a lot of other principles

the goal of DRY is to literally write less code. if you find yourself repeating the same thing over and over, you should wrap that code in a maintainable function or class. the point being, should you need to CHANGE that code, you only need to do it in one place, and not the 82394832 different places that use that logic

have a good idea of what procedural vs functional vs object oriented programming is

procedural has some benefits but in most cases its written out of lack of knowledge of good programming principles 

i think data science tends to be pretty functional in the better cases although i’m sure with bigger tasks it benefits from OOP is as well

a lot of the code i tend to write is OOP, which is a whole subject on its own, and is the one that requires the most conscious knowledge of design imo

as such, learning about OOP in general is probably a good step towards learning good software design, but may be out of context for data science usages

note none of these paradigms are mutually exclusive though, if anything they usually all happen at once in some form or another

parameterize things to give flexibility and avoid hard-coded values

this ties in pretty closely to DRY

in data science i think you guys tend to have a lot of “magic number”, e.g. hard-coded values that might represent thresholds or whatever

stop doing that :(

at the very least, extract those numbers as a named constant that you can reference throughout your code, again so if that number is tweaked during development (as it probably will be) you only need to change it once

or, by making it an input to your program, you have the flexibility of executing your algorithm several times with different input parameters to match different situations

from a production standpoint this is valuable because you don’t have to change the internal code/algorithm to get different results, simply the inputs

i feel like that isn’t entirely useful but hopefully it gives you an idea jdklfadj ofc i’m always down to talk about something specific at more length!!! at the end of the day good programming practice comes solely out of experience. you have to do it for yourself and see the inefficiencies for yourself to really understand where you can write “better code”

[lesbianfeminists]

“Health care is a human right.

The Trump administration roll back of anti-discrimination protections in healthcare is a victory for the religious right and a threat to women’s abortion rights.

The health care systems of the US and UK mark the stark differences between their respective social histories and political landscapes. The National Health Service (NHS), a radical gain of post-war social democracy, inspires deep emotional attachment to principles of collective care. We are all responsible for one another. In the US, the political triumph of principles of libertarian individualism and protection of profit, have scuppered attempts to create universal healthcare provision. ‘Obamacare’, vigorously opposed by capital, by republicans and libertarians, massively expanded the provision of insurance but fell short of guaranteeing the human right to health care.

Due to the NHS, fewer people in the UK face anxiety of healthcare-related debt and insecurity commonly experienced in the US. However, we are still very far from treating health care as a human right. Even as some NHS Trusts rightly raise the slogan #BlackLivesMatter and work to understand and address the discrepancies in covid deaths by ethnicity, the NHS continues to enact the government’s racist ‘hostile environment’ with horrendous results. The NHS charging regime is a central plank of this policy, with Trusts now obliged to to check the immigration status of patients and bill those who are not able to prove their entitlement. For pregnant women, this can mean bills of tens of thousands of pounds for maternity care.

The UK Equality Act explicitly provides for single-sex exemptions to an anti-discrimination framework that covers race, religion and belief, age, disability, sex, pregnancy and maternity, marriage and civil partnership, sexual orientation and gender reassignment. While there has been concerted effort to interpret and apply this law in ways that simultaneously undercut single-sex exemptions while broadening the scope of discrimination on grounds of gender reassignment to the point of encroaching on sex, it provides a potential framework for balancing conflicting rights. In contrast, US anti-discrimination law has proceeded by a complex patchwork and accretion of legal cases, legislation and constitutional amendment, across federal, state and local jurisdictions that overlap.

In the US neither sexual orientation nor gender identity are protected by federal legislation. In the absence of specific anti-discrimination law, the US Department of Health and Human Services (HHS) had, in 2016, issued a new rule that prohibited “the denial of health care or health coverage based on an individual’s sex, including discrimination based on pregnancy, gender identity, and sex stereotyping.” Just as extending marriage rights to same sex couples is an imperfect mechanism to expand healthcare coverage, increasing the scope of sex discrimination to cover gender identity is not a perfect mechanism to extend needed protections to groups that are not otherwise protected.

The 2016 HHS rule also stated that the Office for Civil Rights would admit complaints of discrimination on the basis of sexual orientation, utilising sex stereotyping as sex discrimination. This chimes with the long-held view of radical gay liberationists and of some feminists that the oppression of women and the sex role stereotyping of compulsory heterosexuality is the root of anti-homosexual prejudice and discrimination. The same rule, while upholding existing protections for religious freedom and conscience declined to expand them.

US feminists have long pointed out the dangers of overbroad legal definitions eliding sex and gender as well as the need for clearly defined rights of women and girls to single-sex spaces. The additional HHS requirement that ‘health programs and activities…treat individuals consistent with their gender identity’ is an example of just such an overbroad definition with potential for real harm, not least to transgender individuals. The failure to identify a transman as pregnant, resulting in stillbirth, is a recent US example of the dangers of treatment consistent with gender identity rather than a sex.

The principle of universal access to health care without discrimination, need not imply support for any and every treatment or intervention. In the era before the NHS, Archibald Cochrane, a founder of evidence-based medicine, raised the slogan ‘All effective treatment must be free.’ The human right to healthcare includes the right to care that is evidence-based and ethical, that heals not harms, and that has our informed consent. The history of healthcare contains not only uplifting stories of human ingenuity and compassion of which we can be proud, but also the scandals of iatrogenic injury from which we must not turn away. Survivors of symphysiotomy, a hugely damaging obstetric procedure favoured in mid-twentieth century Ireland over caesarean section for ideological reasons, and women damaged by vaginal mesh implants are two groups harmed by treatments performed with insufficient scrutiny.

This week, the Trump administration, following legal victories by the religious right, reversed this rule. The denial of healthcare or healthcare coverage based on pregnancy, gender identity and sex stereotyping (including sexual orientation) is no longer prohibited and new exemptions have been added that allow health care providers to invoke religious objections to service provision. This is not about specific transgender health treatments, but about protection from discrimination in relation to any healthcare. Health care is a human right.

Some who support sex-based rights are misguidedly applauding this change in the US government position, despite the fact that it actively harms lesbians, women seeking abortions and women who defy gender norms, and despite the fact that it represents no benefit to women. The endorsement of ‘sex not gender’ in ACA anti-discrimination rules sets no precedent for the hundreds of pieces of state and local legislation on the books which will continue to elide sex and gender to the detriment of women. The victory belongs to a religious right who are waging a war on women and against the principle of health care as a human right.”

Health care is a human right: Judith Green

Judith Green is a co-founder of Woman’s Place UK, works in women’s health and is a former user of single-sex services for female survivors o

[redbeardace]

August TAAAP Chat Notes:  Sex Ed

This is a scattered bunch of thoughts and notes on some of the things that were discussed about sex ed in the August TAAAP Pride Chats.  There’s no solid thesis here, but maybe a few conversation starters.  Some of what’s here is a post-chat thought and wasn’t even discussed at all.  This should also be taken as incomplete and not a full overview of what was discussed.  (Notably, it doesn’t include much of what went on in the voice chats.) 

[Cross-posted from Pillowfort.]

Include aces and aros.  Unsurprisingly, one of the main things was that aces and aros should be included in sex ed courses.

Sex ed has gone backwards since the early 90s?  Either I had a wildly advanced program in my schools (in a deeply conservative rural area), or the fallout of Jocelyn Elders and the “abstinence-only” nonsense of the Bush years completely obliterated the usefulness of sex ed.  We had a program that spanned multiple years, starting with a single day vocabulary lesson and “puberty is coming!” warnings in the 5th or 6th grade, through a two week lesson about all sorts of things in 9th or 10th grade health class.  We were told that masturbation and gay people and condoms and oral sex existed, although there were no details about how any of those things worked.  It wasn’t perfect, but it was a start.  But a lot of the people in the chats were talking about their sex ed, and it sounded woefully, frighteningly inadequate.

What is “sex ed”, anyway?  School, teaching the basics?  Information for adults?  Training courses for professionals?

Cover the basics.  The basics are important.  Anatomy, menstruation, common medical issues down there.  Cover what’s “normal” and what should be taken to a doctor.

What about other classes?  How can a math teacher express support?  Hang a flag.  Tackle amatonormativity in story problems.  Discuss it in the staff room.  Point the sex ed teachers at aro/ace resources.  Be out.   Stories about aromantic people read in English class.  Asexual people talked about in history.  GSAs/Pride groups in school that are aro and ace inclusive.

Desire for sex or romance are not universals.  Stop with the “Everyone wants it eventually”, and switch to something more like “a lot of people do, but not everyone, and it’s okay if you don’t.”

Reframe the discussion of “No”.  Too often, in sex ed, it’s all about when you’re “ready”, with the implication that you will be “ready” one day.  And when you’re “ready”, there’s the implication that you’re ready and willing for everything from that point forward.  Like if you say “yes” to a date and you’ve opted in to all the romancey things, say “yes” to sex and you’ve opted in to all the sexy things.  That’s not right.  It should be more focused on what you want to do, and empower people to say “no” to things they don’t want.  Discuss reasons for saying no, include “I just don’t wanna”.  Normalize the permanent “no”.

Look for backdoor opportunities for inclusion.  For example, the new Washington State Comprehensive Sex Ed law requires teaching of sexual orientations and gender identities as listed in the definition used by another section of state law.  So if that other section gets updated to include aros and aces, the sex ed curriculum will also have to be updated.

Connect with the people doing the work.  There are groups who build sex ed programs and lobby for them.  Work with them to include ace and aro topics.

Beware the head-in-the-sand crowd.  There is a very loud, very active anti-sex-ed lobby out there.  In WA, they got the sex ed law put up for a vote. Some of their objections are that affirmative consent goes against their religious teachings, and that although they can opt out their kids from the lesson, they can’t opt out their kids from schoolyard talk, so your kids have to remain ignorant, too.

Fuck you, Kemper Freeman.  Seriously.  Fuck that guy.

How do you accommodate varying levels of interest and aversion, while still providing necessary levels of detail?  The topic of sex ed is a bit of a minefield.  Some people want to know all the things, some people want to know very very little.  Some topics are dysphoria triggers, some topics are aversion triggers, some topics are just not interesting or of any practical use.  There’s a baseline of information that everyone should know, and there’s a level of detail that the interested people should get.  But how do you do that in a classroom setting?  One suggestion was to allow people to freely step outside for certain topics.  Another was to have an interactive lesson, where the student is able to adjust the detail based on their comfort level and interest.  It would start out with a “default” level of detail, but would allow the student to request less detail or more detail for each topic.  The less detail level would still have all of the baseline level information that everyone should know, while the more detail would go beyond a surface level summary.  Likewise, images could be switched between text description, line art diagrams, and actual photos.  

Resources!  Scarleteen, Sexplanations, etc.

Discuss healthy relationships and consent.  Provide practical examples.  Not just how/when to say yes or no, but how to bring up things you want to do or are curious about.  Include queer relationships.   How to ask for what you want.  How to know what you want.  How to say no to what you don’t want.  All relationships, not just sexual or romantic.

Reconsider segregation by gender.  A lot of sex ed is done with a gender split, but does it need to be?  If there is a value to such a split, how can it be made trans and intersex supportive?

Bring up body variations.  There’s a wide variety of genital configurations, so mention them.  Discuss intersex bodies.  Discuss small parts, large parts, asymmetrical parts.  This would likely be an appropriate place to include actual photos, because so many people said that actual photos were only used in the STD scare tactics.

Elaborate on “sex”.  Too often, it’s discussed as just PIV to orgasm and that’s that.  But what about things that don’t involve Ps or Vs or do involve Ps and Vs, but not the I?  What about stuff before and after?  What alternatives are there if you don’t like certain aspects but are fine with others?

Cover everyone.  If there is a separation, each group should cover the same things, at least at some level.  Everyone should come out of sex ed knowing about their own body and its processes, as well as about bodies they don’t have, and their processes.

Don’t “teach” through fear.  STDs are bad, but they’re preventable with caution and mostly treatable in some form or another.  Pregnancy typically isn’t desirable for high schoolers, but here’s a dozen ways to avoid it.  Give direct information, don’t try to terrify people.

Mention pleasure.  Mention the basics of obtaining pleasure, whether alone or with others.  If anyone walks out of a sex ed course of any kind without knowing about the clitoris, it’s a failure.  People should know that most clitoris owners can masturbate, and can experience pleasure from sexual acts, if done the right way..

Dispel myths and lies.  Not everybody wants it.  Vaginal penetration isn’t necessarily going to lead to orgasm.  It’s not supposed to hurt the first time.  You don’t have to have an orgasm.  It’s okay not to know what to do.  “Girls don’t want it.”  “Boys will be boys.”

Toys.  AFAB people don’t have to only use vibrators to masturbate.  AMAB people can use toys.

What is “Attraction”?  And along those lines, what is “Libido”?  What do these things feel like?  How do you know what you’re feeling?  What are these experiences like for different people?

Hygiene.  Give information about keeping various zones clean.  Talk about the results of various activities, partnered or not, and what steps might need to be taken.

Porn is fake.  Watching porn to pick up information about how to do sex is roughly equivalent to watching a crime procedural to learn how to become a cop.  You’ll get a very skewed view of things.  Pleasure isn’t always visible or audible.

Destigmatize it all.  Sex is seen as taboo and secret, and not to be spoken of, and that attitude harms people.  It prevents them from feeling comfortable to bring up important things or ask important questions.  It prevents them from learning things they need to learn.  It forces people into bad situations and mediocre encounters because they don’t know it doesn’t have to be like that.

Teach people how to learn.  Sex is currently a subject fraught with misinformation.  Porn or Cosmo are main sources of information, yet aren’t super accurate.  People should be given tools to know how to find and evaluate the information.

Consent is bigger than the bedroom.  Consent includes touch, jokes, conversations, etc.  It’s anywhere boundaries exist.

More than just cis white male voices.  So much of sex ed is heteronormative, amatonormative, tailored for specific cases, and mired in the ignorance of the past.  Sex ed needs more perspectives.

[heywannalearn]

Hello darling, I know you are so busy and I truly respect that so, if you don't want to answer it's all fine. My question is how I can convert program code from language to other for instance; c++ to python. And if you know how could I DM you with example? With all my respect and love

Hey hey!

I’m not sure what your experience and background with code is, so I’ll explain as if I’m talking to somebody who doesn’t know much. So, there’s quite a bit of difference between a language like C++ and python. I’m much more familiar with Python, but I’ll do my best to answer:

Biggest question: why do you want to convert this code? 

If you’re talking about taking a source language and converting it into another source language, you’re probably thinking of “source-to-source compiler” (Wiki Link: https://en.wikipedia.org/wiki/Source-to-source_compiler). Sometimes called “transpilers”.

There are a few reasons why it might be hard (or easier) to convert your code:

1. The Types of Languages You’re Converting C++ is an extension of the C language. The code appears much longer and more drawn out than Python, which can be pretty short. For example:

(Image from Google Images)

I’ve never messed with C or anything like it. C++ as I understand it is both procedural and object-oriented since it added “abstractions” to the original C. Looking at the documentation, it’s quite different from what I’m used to in web dev.

2. These things exist! Sort of. For some things, there’s no such thing as a perfect service or app that will convert your languages. For other languages, there are successful examples of transpilers.

There’s a popular transpiler called Coffeescript, for example: “CoffeeScript is a programming language that transcompiles to JavaScript. It adds syntactic sugar inspired by Ruby, Python and Haskell in an effort to enhance JavaScript's brevity and readability.[4] Specific additional features include list comprehension and pattern matching.” (Source: wiki - https://en.wikipedia.org/wiki/CoffeeScript)

However, the difference between C++ and Python is a much wider gap than something like Coffeescript and Javascript. How big is that difference? I couldn’t say, but looking at the documentation for C++ and looking on Google, I would venture that it’s a wide gap right now.

Well, if you search “convert C++ to Python” there seems to be a few options out there, but based on my cursory research: these programs can be clunky and ineffective depending on what you’re trying to accomplish. Again, that goes back to my question: what is it for? Many users have asked the same question and basically been told: “Learn C++, pay someone, or post tiny bits of codes to forum for help.” This seems to be the general sentiment from StackOverflow and other coding forums. 

See relevant StackOverflow questions here:

https://www.quora.com/Is-there-something-which-converts-code-of-one-language-to-other

https://stackoverflow.com/questions/11792529/c-to-simpler-language-python-lua-etc-converter

https://meta.stackoverflow.com/questions/296119/is-how-do-i-convert-code-from-this-language-to-this-language-too-broad

Based off all that: I would suggest getting some help through forums (Reddit, Discord groups, StackOverflow) for small tidbits, learning it to translate it yourself, or paying someone to. 

Whatever happens, try your best! Good luck!

-heywannalearn

P.S. If any other CS nerds wanna get in here on this, let me know. I don’t know as much about converting languages that are more procedural like C, C++, etc. since I’m largely focused on web dev.

[confrontingbabble-on]

Combating irrationality...is the fastest way to get to reality...

“The following  briefly describes some of the most common fallacies:

ad hominem: Latin for "to the man." An arguer  who uses ad hominems attacks the person instead of the argument.  Whenever an arguer cannot defend his position with evidence,  facts or reason, he or she may resort to attacking an opponent  either through: labeling, straw man arguments, name calling,  offensive remarks and anger.

appeal to ignorance (argumentum ex silentio) appealing  to ignorance as evidence for something. (e.g., We have no evidence  that God doesn't exist, therefore, he must exist. Or: Because  we have no knowledge of alien visitors, that means they do not  exist). Ignorance about something says nothing about its existence  or non-existence.

argument from omniscience: (e.g., All people believe  in something. Everyone knows that.) An arguer would need omniscience  to know about everyone's beliefs or disbeliefs or about their  knowledge. Beware of words like "all," "everyone,"  "everything," "absolute."

appeal to faith: (e.g., if you have no faith, you cannot  learn) if the arguer relies on faith as the bases of his argument,  then you can gain little from further discussion. Faith, by definition,  relies on a belief that does not rest on logic or evidence. Faith  depends on irrational thought and produces intransigence.

appeal to tradition (similar to the bandwagon fallacy):  (e.g., astrology, religion, slavery) just because people practice  a tradition, says nothing about its viability.

argument from authority (argumentum ad verecundiam):  using the words of an "expert" or authority as the  bases of the argument instead of using the logic or evidence  that supports an argument. (e.g., Professor so-and-so believes  in creation-science.) Simply because an authority makes a claim  does not necessarily mean he got it right. If an arguer presents  the testimony from an expert, look to see if it accompanies reason  and sources of evidence behind it.

Appeal to consequences (argumentum ad consequentiam): an argument that concludes a premise (usually a belief) as either true or false based on whether the premise leads to  desirable or undesirable consequences. Example: some religious people believe that knowledge of evolution leads to immorality, therefore evolution proves false. Even if teaching evolution did lead to immorality, it would not imply a falsehood of evolution.

argument from adverse consequences: (e.g., We should  judge the accused as guilty, otherwise others will commit similar  crimes) Just because a repugnant crime or act occurred, does  not necessarily mean that a defendant committed the crime or  that we should judge him guilty. (Or: disasters occur because  God punishes non-believers; therefore, we should all believe  in God) Just because calamities or tragedies occur, says nothing  about the existence of gods or that we should believe in a certain  way.

argumentum ad baculum: An argument based on an appeal  to fear or a threat. (e.g., If you don't believe in God, you'll  burn in hell)

argumentum ad ignorantiam: A misleading argument used  in reliance on people's ignorance.

argumentum ad populum: An argument aimed to sway popular  support by appealing to sentimental weakness rather than facts  and reasons. This can lead to bandwagon fallacies (see below).

bandwagon fallacy: concluding that an idea has merit  simply because many people believe it or practice it. (e.g.,  Most people believe in a god; therefore, it must prove true.)  Simply because many people may believe something says nothing  about the fact of that something. For example many people during  the Black plague believed that demons caused disease. The number  of believers say nothing at all about the cause of disease.

begging the question (or assuming the answer): (e.g.,  We must encourage our youth to worship God to instill moral behavior.)  But does religion and worship actually produce moral behavior?

circular reasoning: stating in one's proposition that  which one aims to prove. (e.g. God exists because the Bible says  so; the Bible exists because God influenced it.)

composition fallacy: when the conclusion of an argument  depends on an erroneous characteristic from parts of something  to the whole or vice versa. (e.g., Humans have consciousness  and human bodies and brains consist of atoms; therefore, atoms  have consciousness. Or: a word processor program consists of  many bytes; therefore a byte forms a fraction of a word processor.)

confirmation bias (similar to observational selection):  This refers to a form of selective thinking that focuses on evidence  that supports what believers already believe while ignoring evidence  that refutes their beliefs. Confirmation bias plays a stronger  role when people base their beliefs upon faith, tradition and  prejudice. For example, if someone believes in the power of prayer,  the believer will notice the few "answered" prayers  while ignoring the majority of unanswered prayers (which would  indicate that prayer has no more value than random chance at  worst or a placebo effect, when applied to health effects, at  best).

confusion of correlation and causation: (e.g., More  men play chess than women, therefore, men make better chess players  than women. Or: Children who watch violence on TV tend to act  violently when they grow up.) But does television programming  cause violence or do violence oriented children prefer to watch  violent programs? Perhaps an entirely different reason creates  violence not related to television at all. Stephen Jay Gould  called the invalid assumption that correlation implies cause  as "probably among the two or three most serious and common  errors of human reasoning" (The  Mismeasure of Man).

excluded middle (or false dichotomy): considering only  the extremes. Many people use Aristotelian either/or logic tending  to describe in terms of up/down, black/white, true/false, love/hate,  etc. (e.g., You either like it or you don't. He either stands  guilty or not guilty.) Many times, a continuum occurs between  the extremes that people fail to see. The universe also contains  many "maybes."

half truths (suppressed evidence): A statement usually  intended to deceive that omits some of the facts necessary for  an accurate description.

loaded questions: embodies an assumption that, if answered,  indicates an implied agreement. (e.g., Have you stopped beating  your wife yet?)

meaningless question: (e.g., "How high is up?"  "Is everything possible?") "Up" describes  a direction, not a measurable entity. If everything proved possible,  then the possibility exists for the impossible, a contradiction.  Although everything may not prove possible, there may occur an  infinite number of possibilities as well as an infinite number  of impossibilities. Many meaningless questions include empty  words such as "is," "are," "were,"  "was," "am," "be," or "been."

misunderstanding the nature of statistics: (e.g., the  majority of people in the United States die in hospitals, therefore,  stay out of them.) "Statistics show that of those who contract  the habit of eating, very few survive." -- Wallace Irwin  

non sequitur: Latin for "It does not follow."    An inference or conclusion that does not follow from established    premises or evidence. (e.g., there occured an increase of births    during the full moon. Conclusion: full moons cause birth rates    to rise.) But does a full moon actually cause more births, or    did it occur for other reasons, perhaps from expected statistical  variations?

no true Christian (no true Scotsman): an informal logical fallacy, an ad hoc attempt to retain an unreasoned assertion. When faced with an example, rather than denying it, this fallacy  excludes the specific case without reference to any  objective rule. Example: Many Christians in history have started wars. Reply: Well no true Christian would ever start a war.  

observational selection (similar to confirmation bias):    pointing out favorable circumstances while ignoring the unfavorable.    Anyone who goes to Las Vegas gambling casinos will see people    winning at the tables and slots. The casino managers make sure    to install bells and whistles to announce the victors, while    the losers never get mentioned. This may lead one to conclude    that the chances of winning appear good while in actually just  the reverse holds true.

post hoc, ergo propter hoc: Latin for "It happened  after, so it was caused by." Similar to a non sequitur,  but time dependent. (e.g. She got sick after she visited China,  so something in China caused her sickness.) Perhaps her sickness  derived from something entirely independent from China.

proving non-existence: when an arguer cannot provide  the evidence for his claims, he may challenge his opponent to  prove it doesn't exist (e.g., prove God doesn't exist; prove  UFO's haven't visited earth, etc.). Although one may prove non-existence  in special limitations, such as showing that a box does not contain  certain items, one cannot prove universal or absolute non-existence,  or non-existence out of ignorance. One cannot prove something  that does not exist. The proof of existence must come from those  who make the claims.

red herring: when the arguer diverts the attention  by changing the subject.

reification fallacy: when people treat an abstract  belief or hypothetical construct as if it represented a concrete  event or physical entity. Examples: IQ tests as an actual measure  of intelligence; the concept of race (even though genetic attributes  exist), from the chosen combination of attributes or the  labeling of a group of people, come from abstract social constructs;  Astrology; god(s); Jesus; Santa Claus, black race, white race, etc.

slippery slope: a change in procedure, law, or action,  will result in adverse consequences. (e.g., If we allow doctor  assisted suicide, then eventually the government will control  how we die.) It does not necessarily follow that just because  we make changes that a slippery slope will occur.

special pleading: the assertion of new or special matter  to offset the opposing party's allegations. A presentation of  an argument that emphasizes only a favorable or single aspect  of the question at issue. (e.g. How can God create so much suffering  in the world? Answer: You have to understand that God moves in  mysterious ways and we have no privilege to this knowledge. Or:  Horoscopes work, but you have to understand the theory behind  it.)

statistics of small numbers: similar to observational  selection (e.g., My parents smoked all their lives and they never  got cancer. Or: I don't care what others say about Yugos, my  Yugo has never had a problem.) Simply because someone can point  to a few favorable numbers says nothing about the overall chances.

straw man: creating a false or made up scenario and then attacking  it. (e.g., Evolutionists think that everything came about by  random chance.) Most evolutionists think in terms of natural  selection which may involve incidental elements, but does not  depend entirely on random chance. Painting your opponent with  false colors only deflects the purpose of the argument. (From the email that I get on NoBeliefs.com this appears as the most common fallacy of all.)

two wrongs make a right: trying to justify what we  did by accusing someone else of doing the same. (e.g. how can  you judge my actions when you do exactly the same thing?) The  guilt of the accuser has no relevance to the discussion.

Use-mention error: confusing a word or a concept with something that supposedly exists. For example an essay on THE HISTORY OF GOD does not refer to an actual god, but rather the history of the concept of god in human culture. (To avoid  confusion, people usually put the word or phrase in quotations.

_______________________

Science attempts to apply some of the following criteria:

1) Skepticism of unsupported claims

2) Combination of an open mind with critical thinking

3) Attempts to repeat experimental results.

4) Requires testability

5) Seeks out falsifying data that would disprove a hypothesis

6) Uses descriptive language

7) Performs controlled experiments

8) Self-correcting

9) Relies on evidence and reason

10) Makes no claim for absolute or certain knowledge

11) Produces useful knowledge

Pseudoscience and religion relies on some of the following  criteria:

1) Has a negative attitude to skepticism

2) Does not require critical thinking

3) Does not require experimental repeatability

4) Does not require tests

5) Does not accept falsifying data that would disprove a hypothesis

6) Uses vague language

7) Relies on anecdotal evidence

8) No self-correction

9) Relies on belief and faith

10) Makes absolute claims

11) Produces no useful knowledge”

https://www.nobeliefs.com/fallacies.htm

[fixittk-blog]

Enough with the microservices

Introduction

Much has been composed on the advantages and disadvantages of microservices, however shockingly regardless i'm considering them to be something being sought after in a freight clique mold in the development organize startup world. At the danger of revamping Martin Fowler's Microservice Premium article, I thought it is great to review a few considerations with the goal that I can send them to customers when the subject emerges, and ideally enable individuals to maintain a strategic distance from a portion of the missteps I've seen. The error of picking a way towards a given engineering or innovation on the premise of alleged prescribed procedures articles discovered online is an exorbitant one, and in the event that I can enable a solitary organization to maintain a strategic distance from it at that point composing this will have been justified, despite all the trouble.

Setting

Microservices are still (shockingly) presently a major thing and a tech trendy expression of the day. The approach has been around always (Service-Oriented engineering anybody?) yet for the vast majority of the organizations I experience, microservices aren't just an exercise in futility or a diversion. They really exacerbate the situation.

This may appear to be weird, on the grounds that the vast majority of the articles on microservices are praising their innumerable excellencies like decoupling tech frameworks, better level versatility, expelling conditions between advancement groups, et cetera. In case you're the measure of Uber, Airbnb, Facebook, or Twitter, at that point that is all most likely genuine. I've helped bigger associations with their microservices moves, including helping them set up informing frameworks and different advances which take into consideration astounding versatility properties. In any case, for development arrange new companies, the majority of that innovation, and those microservices, are seldom required.

You are not Netflix, quit attempting to be them!

–Russ Miles

Russ Miles makes this his initially point in his post on 8 approaches to lose at microservices appropriation, and it's something I see constantly. Development arrange new businesses regularly need to copy the prescribed procedures they see at those organizations, frequently to their own impediment. Best practices are setting subordinate. What is a best practice for an organization like Facebook, could conceivably be a best practice for a startup with an aggregate designing group size of 100 or less.

Regardless of the possibility that you are littler than the tech monsters, despite everything you may, on the adjust, move some advantage from towards a microservices design. In any case, a development arrange startup doing a discount movement to microservices ought to be a terminating level offense for the tech individuals included.

Why microservices?

More often than not, in development organize new companies, the fundamental inspiration for moving to microservices is that expectation that doing as such will evacuate conditions between advancement groups as well as enhance the capacity of the framework to deal with bigger activity loads (i.e., adaptability). Normal grievances and side effects are things like union clashes, bugs in arrangement because of parts of the application not being prepared to utilize in part actualized components, and even adaptability. How about we separate these exclusively.

Conditions

In an early-arrange startup, the dev group is little and the tech is little. Individuals can function admirably together without venturing on toes and it appears as though everything is moderately quick to actualize. Life is great.

As the startup develops, the dev group develops, and the codebase develops, and soon there are different groups taking a shot at the same codebase. These groups are regularly generally made out of the general population who were around at the prior phase of the startup. Since some early-organize new businesses are a first occupation for some lesser designers, they don't understand that the correspondence adequacy needs to increment as the group measure and codebase estimate increments. As is frequently the case for tech individuals who have restricted understanding, they go after a specialized answer for a people issue, and choose they require microservices keeping in mind the end goal to lessen conditions or coupling between dev groups.

In actuality, they have to address the general population related issues by means of more viable correspondence. At the point when a startup has different dev groups, it is a prerequisite that they remain facilitated and educated about everybody's work. They have to work together. Programming improvement, in any association of this size, is a social attempt. On the off chance that there is little correspondence or data sharing between groups, they will have a similar reliance issues, with or without the microservices. Nonetheless, with the microservices, they will likewise have the majority of the negative specialized issues that come appended.

Without a doubt keeping the code particular, as a tech answer for the issue, can alleviate a portion of the between group conditions characteristic in programming advancement, yet the correspondence segment still should be developed and enhanced as the group measure develops.

Try not to mistake decoupling for circulation. You can accomplish decoupling by having a stone monument, made out of very much characterized modules, with all around characterized interfaces, and you ought to. You don't have to circulate your application as discrete administrations keeping in mind the end goal to profit by the decoupling you get by having modules with clear interfaces.

Fractional component execution

This point is regularly tended to by highlight banners, which are something you may should be acquainted with to effectively execute microservices at any rate. Particularly as you get into fast arrangement (talked about additional beneath), you may need to convey parts of components which are not yet prepared on specific stages, or where the frontend usage is finished however that backend is not, et cetera. As organizations develop, and sending and operations frameworks turn out to be more computerized and complex, include banners are something critical to utilize and to utilize astutely.

Flat adaptability

This point has some legitimacy in that numerous duplicates of a similar microservice can be conveyed with a specific end goal to accomplish a type of adaptability. Nonetheless, most organizations that receive microservices too soon will utilize a similar stockpiling subsystem (regularly a database) to back the majority of their microservices. This means you don't generally have flat adaptability for your application, just for your administration. In the event that this is the adaptability technique you plan to utilize, why not simply convey more duplicates of your stone monument behind a heap balancer? You'll finish a similar objective with less multifaceted nature. That, as well as the multifaceted nature that goes with flat adaptability ought to just be borne if all else fails. Your first exertion ought to be in finding a way to enhance your application execution. Regularly, even essential things can bring about execution several times quicker than the first framework, and that likewise incorporates shrewdly utilizing administrations which bolster your application. I said in my post on Redis execution triage, for instance.

Is it true that we are prepared for microservices?

This question is regularly never at any point considered while pondering what a design ought to look like, yet it ought to be. Ordinarily, the senior technologists in an organization just distinguish grievances or agony purposes of engineers or of the business, and afterward discover something on the Internet asserting microservices designs address those issues. This claim has numerous admonitions. Microservices, in the same way as other things, accompanied positive and negative impacts. In the event that your association is develop enough, and has the tech set up, at that point the difficulties related with having microservices can be limited, making the beneficial outcomes all the more evident. So what is being prepared for microservices? Martin Fowler recorded his Microservice Prerequisites years prior, and as far as I can tell most development stage new businesses have completely disregarded him. Martin's requirements are a decent place to begin, so how about we think of them as.

Quick provisioning

Essential checking

Quick sending

I can let you know as a matter of fact with many development arrange new businesses that none of them have even one of these essentials set up, it doesn't mind every one of them. On the off chance that your tech group doesn't be able to rapidly arrangement, convey, and screen the majority of your present frameworks, you should pick up that capacity before you consider relocating to microservices. How about we consider each of these requirements in more fine grained detail.

Fast provisioning

On the off chance that your association has just a single or a couple people in your whole dev group who can set up new administrations, virtual or else, you are not prepared for microservices. You will require various individuals in each group with the capacity to arrangement framework and send administrations to that foundation without requiring outside help. Keep in mind, in the event that you have a DevOps Team, at that point you are in no way, shape or form doing DevOps. Designers ought to be required in overseeing everything about their applications, including foundation.

In like manner, if your present design is not upheld by adaptable framework that is anything but difficult to scale here and there and can be overseen by different individuals in the groups, you should address this before moving towards microservices. You can obviously have microservices running all alone exposed metal machines, and you may have prevalent execution for lower cost, yet you should in any case have the capacity to have adaptability on operations and sending of your administrations.

Essential observing

In the event that you don't screen the framework and application execution of your stone monument, at that point you will have a hopeless time with microservices. You require nature with framework level measurements, (for example, CPU and RAM), application level measurements, (for example, ask for inactivity per endpoint, or mistakes per endpoint), and business level measurements, (for example, exchanges every second, or income every second) to comprehend the execution of your frameworks. For every one of the complexities of the stone monument, an outfit of microservices is much more intricate to comprehend, not to mention investigate, with regards to execution. Set up something like Prometheus and add all the important instrumentation to your stone monument before cutting parts of it out into microservices.

Fast organization

On the off chance that you don't have a decent nonstop mix and arrangement process and framework set up for your stone monument, at that point attempting to oversee mix and deplo