88 karma · joined February 12, 2021
If I make a law to allow people to own air, then people start renting out the air and living off of the income of renting air. That's where your archaic Adam Smith model of the economy completely fails.
Under your idealistic model there's no concept of an unfair transaction because all parties benefited from the transaction. One person can breath so he's happy, another person got money from renting air so he's happy. Everyone is happy, so the concept of getting ripped off doesn't exist.
No I told you the risk is nothing. I just have capital to make a down payment that's it. Additionally risk isn't an economic product. How risky something is does not contribute extra GDP to the economy. Only productive work contributes to the economy.
>If your landlord is not providing you a valuable service, cut him out. Vertical integration is a time-proven way to remove middlemen that don't add value. The fact you are aware of the alternatives and that they are easy and yet you choose to continue paying rent shows it is valuable to you.
It is valuable to me. Your statement proves nothing. It's similar to how air is valuable to me. Take the concept of property ownership and place it on air. Now I have to pay some owner of air money because he is providing me a valuable service of letting me breath his air?
I'm not providing a "service" to anyone anymore than a hypothetical owner of oxygen is providing a "service" to let people breath.
>We all have incomes that far exceed one person's labor, because of the benefits of specialization and free exchange, which are still fundamental to economics. The stored surplus is capital, which further magnifies productivity, and is necessary for any modern lifestyle - without it, we'd be a lot more equal, but it would be the equality of hunter-gatherers.
No we don't. I'm not talking about income from manual labor of one hunter gatherer. I'm talking about the average possible income one man can make without hiring any employees or investing in capital in a modern economy. I thought this was obvious, guess not.
Many people make less than this, many people make significantly more. The people who make significantly more tend to have had hired human capital to produce output equivalent to multitudes of people.
>If your landlord is not providing you a valuable service, cut him out. Vertical integration is a time-proven way to remove middlemen that don't add value. The fact you are aware of the alternatives and that they are easy and yet you choose to continue paying rent shows it is valuable to you.
No it's not. Dude. By middleman I'm not talking about some hustler who connects two potential clients together or fronts some kind of risk. I'm talking about people who are sitting on tons of investment capital and just living off the growth of that capital by doing Zero work.
Warren Buffet invests in low low risk companies and profits off the growth of these investments by doing no work. Literally if warren buffet didn't exist the world wouldn't really change... If Elon Musk didn't exist on the other hand, the space industry and automobile industry would be very different.
Warren Buffet by owning a bunch of stock from a lot of companies isn't contributing anything to the economy. No services, no risk, no nothing. He's just benefiting from the growth of others peoples' work.
Both of these people benefit from human capital but warren is the more apt example because he doesn't even contribute anything to the investments he owns. He's just a stock picker.
Whatever you think about the economy this much is real: It's already officially known that the wealth inequality is the result of income from capital growing faster than income from productive labor.
It's free money in every sense of the word. And because productive capital is the basis of an economy what you get is wealth inequality.
The land existed before my landlord was alive. It's the equivalent of charging me to breath air because someone owns it.
>You are providing a service your tenants value. In your case, this may be mostly the assumption of risk - what if your tenants stop paying, and the government says you can’t evict? What if rental prices drop dramatically? Or real estate prices drop dramatically? What if your tenants move out and it takes X months to rent?
Sure you could say that I take on the risk, but that's also dependent on data. Historically for the last century the risk is highly minimal. I could also, If I wanted pay off the entire loan. Then there would be no risk. It would essentially become the economic equivalent of me charging people for breathing air that I own.
>You are still on the hook for your payments to the bank, and your equity and credit rating are at risk.
I can afford to pay on my own. Additionally I can sell the property at anytime as well. Of course there is still risk in depreciation but I already know the risk is minimal based off data.
>The bank lending you capital in exchange for interest (rent) is also providing you a valuable service - and you are providing a valuable service to them, giving them a return on their capital (with an acceptable risk of default).
Yeah, a service in exchange for what? For interest. Interest that I don't pay for. The exchange is more between the tenants and the bank and I function as a middle man leaching from the tenants. It is their blood sweat and tears that will be fronting the loan and the house that I will own.
>That’s the “invisible hand” of free market exchanges - each party gives what they value less to obtain what they value more, so both parties are better off (if they didn’t feel themselves to be better off, they would not make the exchange).
The invisible hand is an outdated concept. The world has moved beyond Adam Smith as the data shows that economic systems are far more complicated.
The current status quo belief argues that the average return on investment outpaces productivity-based income by a wide margin. So basically not only does owning property allow me to gain money from it without an ounce of work. But investments on all forms of capital from property to human capital is responsible for much of the wealth inequality that exists today.
Such capital ownership allows people to have incomes that far exceed what any one human individual is capable of generating through productive labor.
What I am saying is that usually in an economic transaction somebody contributed something to the economy. A product was distributed or created. A service was offered or provided.
I offered nothing to the economy. I am simply gaining money by doing nothing.
Also I'm referring to my specific situation where the rental costs are covered fully by rent. If you take on the loan yourself with your own money.. well that's a different situation.
>I know people who are financially literate and have capital who choose to rent.
I also rent. I also never said there was anything wrong with renting. I'm just saying that rent is an economic black hole. No energy was expended to increase GDP in exchange for rent money. I benefit by doing nothing and so does the person who rents to me.
I prefer jetbrains like you, but some people like their apps to be really snappy.
That was a rhetorical question. I beg to differ. English does fill the space of all kinds of of domain specific areas. Practitioners may invent new vocabulary to use within the English language but in the end they are still using English.
In fact even when you talk about "Design patterns" You are still using "English" it's inescapable. I'm saying the extra layer of "design patterns" as a "field" is not necessary. No other "domain" is snobbish enough to call their techniques "patterns" and group them as "design patterns" and fill the field with all this jargon like "strategy pattern." It's just programming techniques, carpentry techniques and the like.
I'm guessing your talking about how iteration is implemented versus the action of iteration. Both are one in the same.
I take it back, everything is a design pattern now. I see the light.
It also seems more reasonable to just leave it as a programming technique rather then give it artificial weight and call it some bloated unnecessary academic term "design pattern"
The more accurate analogy is if you can charge rent to tenants in the property in a way that covers all expenses. Then other then the down payment the tenants are basically letting you leverage an appreciating asset at no cost to you.
I do this now in California and with the essentially 0% interest rate I refinanced the loan and now I generate a profit every month from leveraging an asset on top of the appreciating value.
Rent is the black hole people can use to leach resources away from productivity. Simply by taking a loan and redirecting the economic output of people who live on my property towards the loan I benefit without producing any utility for the economy at all. That is in a sense "Free." If the loan is paid off, that money gets redirected towards me again with minimal effort on my part.
But calling the "naming of things" a "design pattern" is pretentious. Nobody calls Monads the "Monad pattern" and categorizes it as a sub field of "design patterns."
It's just like how we abstract the concept of getting into a car and commanding the car under the word "driving." That's fine. What's wrong is if We called it the "driving pattern" and place it an area of study within the automobile field called "design patterns."
Imagine if some expert race driver publishes a driving book called "Design patterns" then with an analogy relates it to architecture. Why not just call the book "Driving techniques" and eschew the useless analogy?
I'll tell you why the GoF did this. Because "Design patterns" sounds more academic, and the catharsis of realizing the analogy between architecture and programming techniques inflates the perception of what these concepts actually are. In the end these are just programming tricks or techniques.
>The value is in recognising similar structures, communicating them, reusing solutions to already thought through problems etc.
The English language already reuses concepts. You drive cars. You do not call it the "car driving pattern" and make is part of the concept of "design patterns" This is the pointlessness I am referring to.
>Anti-patterns are very useful concept as well.
Yeah in common English you call it "Bad techniques" or "ineffective methods". Everyone is already 100% aware of the concept of a technique that isn't "good" you don't need to teach people this concept. My argument here is that the name "anti-pattern" is pure snobbery. It's like calling standing still "anti-movement."
No new concept was introduced by the word "anti-pattern." Anti-pattern refers to a very simple concept that every single human understands. The pretentiousness is in the word and inflates the perception of this concept to the point where someone like you thinks "anti-pattern" is a completely new mind blowing concept (It's not).
The burden remains on you to validate the argument and ignore your biases as obviously this author and the people who voted him up have their reasons for believing in what they believe.
You're just iterating through a list and calling it "iterating" is perfectly fine.
Don't get me wrong. Naming things to abstract away complexity is perfectly fine and a foundational aspect of the English language.
Naming something the "iterator pattern" and calling it a concept within the sub field of "Design patterns" is the snobbery I'm referring to.
It's like if someone came up with the "Logic pattern" or "Intelligence pattern."
But in computer science they had to basically make the same concept sound more snobbish. These aren't programming techniques, they are "design patterns."
Arguing about a rainbow or arguing about a color in the rainbow doesn't effect the validity of an argument, I'm not sure your analogy makes any fundamental sense here.
>The whole point it to use common vocabulary where you can drop this "pattern" suffix when discussing things.
Isn't this the purpose of the English language? The "Design Pattern" concept is a redundant concept existing recursively in English. English already provides a "common vocabulary" for "discussing things."
What does design patterns provide on top of that? Only additional complexity and redundancy.
That's why basically all fields outside of programming don't really use the word "design pattern" because it's not necessary. It's a bit of snobbish for a pilot to call a flight technique a "design pattern."
>It can be anything,
And that's why it's pointless. There are even design patterns in poetry if you follow this line of logic. The English language is pretty much the "language" designed to be "anything." For a concept within "English" to be useful it must focus on a smaller subset of "anything."
But there's no need to group what is essentially just English Vocabulary into another sub category of "language" prefixed with "design" and then post-fix all internal concepts with "pattern."
Also note that school generally doesn't teach it because these patterns don't have any formal basis in theory. It's the complex vocabulary that gives these things more academic weight than they actually have. "Tricks of the trade" doesn't sound as rigorous as "Design Patterns" but really it's the same thing.
Not true, they build proofs. Within proofs there are many many common techniques, aka "patterns."
Either way you seem to imply that "patterns" are for people who "build" things, which isn't emphasized in your definition below:
>"A pattern language is an organized and coherent set of patterns, each of which describes a problem and the core of a solution that can be used in many ways within a specific field of expertise. The term was coined by architect Christopher Alexander and popularized by his 1977 book A Pattern Language."
The problem with the above definition is that English vocabulary already communicates what a pattern does perfectly fine. What is the point coming up with an over complex name and postfixing all of these things with "pattern?" It's basically a redundant concept.
In fact, my communication with you at this very moment is employing many many common patterns. Check the pattern in the previous sentence "many many." I call it the double emphasis pattern and I've used that pattern twice in this reply. I'll write more about it in my book on Design patterns for English communication.
As of right now my post has 7 upvotes and no downvotes which means 7 people agreed with me. That means either a lot of people didn't read the article or they misread the article like I did.
I wonder how many downvotes my post will get after they read your comment which essentially categorically proves my initial reply is completely and utterly wrong.
Which goes to show how many people just skip over reading the article and go straight to the comment section for a summary/full analysis.
>An 'element of reusable software'
>A design pattern systematically names, motivates, and explains a general design that addresses a recurring design problem in object-oriented systems. It describes the problem, the solution, when to apply the solution, and its consequences. It also gives implementation hints and examples. The solution is a general arrangement of objects and classes that solve the problem. The solution is customized and implemented to solve the problem in a particular context.
Interesting to note that the person defines a pattern as something exclusive to using Objects and classes or in other words OOP. So something like lenses or functors or programming techniques defined outside of OOP are not patterns.
When I talk to people they often define design patterns as a common language for various methods that are common to programming and not exclusive to OOP. Doesn't english and vocabulary fill this space? You don't find carpentry workers referring to domain specific vocabulary as design patterns. Why don't FP practitioners or mathematicians call their techniques "patterns"?
This may piss some people off and get me a load of downvotes, but honestly IMO I find design patterns to be just snobbery. Instead of saying someone is iterating through a list they say that someone is using the iterator pattern. It's really just prefixing the word "pattern" onto some vocabulary. I used the number pattern on the variable pattern and the addition pattern to get the sum of two numbers.
I would've just called the book "Programming Tricks for OOP" rather then "Design Patterns."
In fact that's why those google shuttles exist. Because back then tons and tons of people loved the city so much that they wanted to live in SF while working in Mountain View.
When tech started rising more and more, tech workers started moving into SF turning it into the tech hub that it is today. This upped property values which in turn drove a lot of junkies and homeless people out of the condemned properties as those properties were getting repurposed to take advantage of the growing market.
That's why you see shit on the streets and needles everywhere. Rising property values essentially took what was happening behind closed doors and put it in the middle of the street. Everybody applauds all the social programs offered to the needy by SF until it they see it up close and personal.
So really there's two main root causes for why SF is the shit hole it is today:
1. Excessive amount of tech workers. 2. Drug availability.
The Tech worker thing is new. The Drug problem is old, although I'm not sure how much the recent opioid epidemic contributes to that.
Anyway this seemed like a tangent but to address your point: Companies wanted to move to SF because the tech workers WANTED to live there. The companies relocated based off the location of talent.
The situation today is the end result of a feedback loop produced by Tech companies and Tech workers from 2010 to now. Tech workers move to SF, so companies follow. This causes more workers to follow the companies.
You'll see this correlation everywhere. If companies don't want to be in a certain city, for sure there's an amount of skilled workers who don't want to be there either.
I think you're making a mistake here. Essentially behind the scenes there's one jetbrains IDE. This IDE is a single platform that can take plugins and code in any language and be customizable to your hearts content.
ON the surface however Jetbrains doesn't exactly release this IDE to the public. They deliver different configurations and different defaults on TOP of this IDE, then they lock it down a little and ship each one of these profiles under a different name. All these IDE's are basically different bundles of plugins running on the exact same core platform.
That's why CLion is only a couple years old and still really good. It's because all Jetbrains needed to develop was a plugin and shove it into an existing ecosystem.
This is no different then Vscode when you think about it. Both are coding platforms that can be plugged with new features, it's just that jetbrains locks some of this customization down and sells their IDEs with bundles of plugins that offers a better core experience.
What makes Jetbrains better is this focused and higher quality bundle of features that feels cohesive. What makes jetbrains worse is that this central platform they're developing for is bloated. Everything is slow, takes forever and can lock up.
If Jetbrains just did something to speed up the platform then pretty much IMO it beats anything Vscode has to offer.