406 karma · joined July 30, 2016
There are hundreds of records of censored content which doesn't have anything to do with all that. This is a fact whether you agree with it or not.
But let's also not say that "Twitter has limitations on free speech" because it feels like a misleading euphemism. Free speech is not a spectrum. You either have it or not.
How about we just say that "Twitter doesn't have free speech".
And yes, "it's totally debatable if that's a problem or not". That I agree.
Twitter HAS a free speech problem. This is not controversial. Now you may not agree that Twitter SHOULD allow free speech, but you can not deny that censorship exists on Twitter and it is serving the political agenda of some people.
Mistakes and problems are everywhere. What matters is the sample size. A single anecdote can't say anything about where the bar is set. It's basic statistics.
"Macbooks seem to be the only viable option these days", because I had bad experiences with two non-Macbook computers.
To be fair; I don't think that the author came to that conclusion only from those 2 anecdotes. But still, that is the way the argument is presented. And it really looks absurd.
We are already making good profits from trading & investments but have also just started building various tools, apps, smart contracts, bots and related tech to support our operations and increase our profits even more.
And now is the time to share it with the right people.
Our culture is an engineer & maker culture. We have some people onboard who combined possess a fair understanding of topics such as economics, statistics, investing, trading, psychology, computer science, operating systems, programming, networking, security, devops, the internet, the web, the blockchain, incentive design and tokenomics.
I'm not disclosing the identity of our company (we have no good reason to announce our existence to the public at this time), but I'm disclosing my own identity as I realize that the target audience of this post (hopefully you) needs to know who they would be working with if they pursue this opportunity.
I am an experienced full stack developer, a product engineer having a lot of startup experience, and a significant crypto exposure. Check out my fancy webpage (https://gwn.wtf/mortals.html) to get an idea about whether I'm the kind of guy you'd be interested in hanging out with.
Our development philosophy is to always aim for quality and simplicity with a pragmatic touch when it comes either to the team, product, or processes. (We're influenced by Suckless: https://suckless.org/philosophy/)
A quality team comes before everything. We have a small team of talented generalists with a hacker attitude, a deep understanding of the "web operating system", and a sense of humor. And we're looking to expand this team (but not too much).
We are not looking for the mythical full stack developer who is an expert on everything, say, ES2118, CSS, responsive design, GraphQL, AWS, Kubernetes, Solidity and shit.
Instead we are looking for people who have a proper foundation on programming in general and the web platform, a strong intellectual curiosity, and the experience & ability to make good judgements when it comes either to technology choices, architectural choices, implementation details, analysis, prioritization, and interaction with customers (internal & external). This is what's important. Specifics can be learned. No one cares if you know flexbox or not. Or funky sorting algorithms. Or React hooks. Or NFTs.
We are very selective when it comes to the projects we work on, people we work with, partnerships we establish and tools & ecosystems we build on top of. It's not only about making money but it's about making it while having a pleasant experience & fun, learning stuff that is worth learning, building a proper reputation, investing in projects & ecosystems & people that will increasingly benefit us and be worth our very precious time in the longer term. All while preserving our health & wellbeing of course.
<snip> (Please visit https://gist.github.com/gwn/12cd1b4219ef3f526d3811df1b27c41e for the full version of this ad)
If you like what you've read so far and think you have what it takes to hang out with the likes of us, maybe you should reach out.
Send me a resume / CV preferably with a motivation letter that shows a sign of intelligence / character / whatever you think sets you aside from the common developer. (Turkish accepted)
Seek me out at dev at gwn dot wtf if you want the red pill
Hello nerds! We are a couple of friends who recently founded a research & development & trading company mostly focused on crypto.
We are already making good profits from trading & investments but have also just started building various tools, apps, smart contracts, bots and related tech to support our operations and increase our profits even more.
And now is the time to share it with the right people.
Our culture is an engineer & maker culture. We have some people onboard who combined possess a fair understanding of topics such as economics, statistics, investing, trading, psychology, computer science, operating systems, programming, networking, security, devops, the internet, the web, the blockchain, incentive design and tokenomics.
I'm not disclosing the identity of our company (we have no good reason to announce our existence to the public at this time), but I'm disclosing my own identity as I realize that the target audience of this post (hopefully you) needs to know who they would be working with if they pursue this opportunity.
I am an experienced full stack developer, a product engineer having a lot of startup experience, and a significant crypto exposure. Check out my fancy webpage (https://gwn.wtf/mortals.html) to get an idea about whether I'm the kind of guy you'd be interested in hanging out with.
Our development philosophy is to always aim for quality and simplicity with a pragmatic touch when it comes either to the team, product, or processes. (We're influenced by Suckless: https://suckless.org/philosophy/)
A quality team comes before everything. We have a small team of talented generalists with a hacker attitude, a deep understanding of the "web operating system", and a sense of humor. And we're looking to expand this team (but not too much).
We are not looking for the mythical full stack developer who is an expert on everything, say, ES2118, CSS, responsive design, GraphQL, AWS, Kubernetes, Solidity and shit.
Instead we are looking for people who have a proper foundation on programming in general and the web platform, a strong intellectual curiosity, and the experience & ability to make good judgements when it comes either to technology choices, architectural choices, implementation details, analysis, prioritization, and interaction with customers (internal & external). This is what's important. Specifics can be learned. No one cares if you know flexbox or not. Or funky sorting algorithms. Or React hooks. Or NFTs.
We are very selective when it comes to the projects we work on, people we work with, partnerships we establish and tools & ecosystems we build on top of. It's not only about making money but it's about making it while having a pleasant experience & fun, learning stuff that is worth learning, building a proper reputation, investing in projects & ecosystems & people that will increasingly benefit us and be worth our very precious time in the longer term. All while preserving our health & wellbeing of course.
<snip> (Please visit https://gist.github.com/gwn/12cd1b4219ef3f526d3811df1b27c41e for the full version of this ad)
If you like what you've read so far and think you have what it takes to hang out with the likes of us, maybe you should reach out.
Send me a resume / CV preferably with a motivation letter that shows a sign of intelligence / character / whatever you think sets you aside from the common developer. (Turkish accepted)
Seek me out at dev at gwn dot wtf if you want the red pill
> I also think you're being a little disengenuous
Busted. Yes, I am actually. Honestly I'm doing that as I'm trying hard not to trigger people. (a lot of people here are easily triggered.) But it is just to get better quality responses and to avoid fanatical ones.
We're in an age where the quality of public discussion has decreased significantly. I'm afraid of getting responses that doesn't really contribute to the conversation if I disclose my side especially on topics like this. This is me being politically correct in the name of pragmatism at the cost of ingenuity.
What's Yeadon's profit on all this? He's not alone either. There are a hell lot of people like Yeadon who are spreading "pseudoscience". And the majority of them are doing this at the cost of their professional cancellation. What are their income models? What are their incentives? Are they simply deluded, or "bad people"? Why are they doing this? Who are behind them (if anyone)? It's easy to alienate this kind of people by saying that they are just "fucking conspiracy theorists" and then forget about them, but the questions remain.
On the other side there are people like Bill Gates, Anthony Fauci, CEOs of the vaccine companies, MDs whose jobs depend on their compliance, and similar others who undoubtedly profit from promoting vaccines and government policies. This group's incentive mechanisms are clear.
What do you think are the incentives of the first group?
Please note that I'm not saying there aren't any at all. It's just that I'm not really sure about it so I'm just trying to start a conversation to get opinions from people smarter than me. I'm just a confused guy and not even trying to pick sides anymore.
There is nothing preventing anybody from using design systems with CSS Modules.
The author makes it sound like you need stuff like Tailwind in order to leverage design systems. This is completely misleading.
> I have used Tailwind UI as a starting point and inspiration for my own components.
There are loads of UI libraries you can use as a starting point & inspiration with CSS modules as well.
The concept of a design system is orthogonal from one's styling solution of choice (CSS modules, Tailwind, CSS-in-JS).
The author certainly knows how to write a blog post and does a good job at selling Tailwind. But in my opinion he doesn't have enough experience to give this kind of opinionated advice to others yet.
I agree, but what sets PostCSS apart from other tools is its forward compatibility. Which is a reason to opt for it for many people, including me.
At the end of the day most people will benefit from having vanilla CSS knowledge anyway regardless of any layer they prefer to use on top of it. SASS is such a layer as well as Tailwind. PostCSS is just tomorrow's CSS. It is to CSS what Babel is to Javascript. So using PostCSS instead of SASS is comparable to using Babel instead of for example CoffeeScript.
If one deems that tomorrow's CSS as it currently stands is advanced enough to handle "big, engineered stylesheets", then PostCSS may well be all they need. But I don't think there is a single right answer here.
Agreed
Seems like it reflects a very subjective way that the author wants to implement web apps in.
I mean why should anybody invest so much time to learn alternative syntaxes and configurations to replace HTML, CSS, Javascript, module bundlers, existing SSR solutions etc, all at once??
Every new tech should have a convincing excuse to exist.
We've had the likes of HAML to simplify HTML, CoffeeScript to simplify JS, SASS to simplify CSS. These worked well as they optionally replaced a small part of the stack and took great care not to deviate too much from the underlying tech. They arguably had an acceptable cost/benefit ratio. The costs were little, as they should have been.
And for the stuff that completely introduced a new world such as ELM, Purescript, ClojureScript: ELM brought in established functional programming paradigms while at the same time providing a sensible framework for the common SPA. Purescript made the web accessible to Haskellers. ClojureScript targeted Lispers and made the Clojure ecosystem accessible to them in their web apps.
I don't see how I can justify the use of this "language" other than the fact that the author "likes it this way". Everything seems so arbitrary and the "all in one" approach seems daunting.
Every good developer goes through a "framework building phase" which is a very enjoyable and educative process even if the end product is mostly useless to anybody else other than the author. I think the author is going through theirs. Best of luck.
Thank you for playing the role of the logic police. I guess it can sometimes be unreasonably hard to talk in a simple forum like this in a chill manner without having to deal with people's (IMO) misplaced pedantry. So be it. I'll try to be more scientific the next time.
An argument doesn't assume, but it states. Assumption is something people do. When somebody makes a statement regarding "what an argument assumes", the meaning is that they are speculating beyond what the argument is stating.
So I don't agree with you, but thank you for the discussion.
For me the thinking & debating exercises doesn't have to involve taking a position personally. Sometimes I just want to focus on the argument. My own position & assumptions are irrelevant.
For that reason I don't appreciate it when somebody makes an assumption regarding my assumptions to attack myself instead of focusing on the argument.
I am not assuming that. I was just comparing it to the situation with cars.
> Not all creators are heterosexual males (or otherwise oriented toward females as preferred or even acceptable romantic partners), and even those that are don’t necessarily view women exclusively through the lens of romantic involvement such that that would be the implication of a female name.
I wasn't implying such a thing. But I knew a woke person was going to point it out to me anyway. Funny.
> Janet is named after a character that is expressly not a woman
The logo of the programming language is the face of an attractive woman wearing a lipstick and a fancy hairdo. Also, Janet is portrayed by a woman in the Good Place. Don't tell me that the name of the language has nothing to do with a woman.
> Why are female-coded names a particular issue
I don't think it is an issue. I was just thinking out loud.
Take it easy.
Julia, Janet, Eve...
I understand the guy referring to his car as his "girlfriend" and give it a women's name. I just can't feel the same about tech.
I guess this may be the nerd's way of immortalizing their sweetheart, but if I was a woman I'd rather prefer to be a car and not a programming language.
A programming language doesn't feel much anthropomorphizable to me, let alone lady-like.
Women, what do you think?
Remote: Yes
Willing to relocate: Yes
Technologies: Javascript, Python, Node, React, React Native, D3, Postgres, advanced SQL, Linux, Containers, Microservices, Serverless, WebRTC, Ethereum, Cosmos
Résumé/CV: http://gwn.wtf/resume.html
Email: dev at gwn dot wtf
Balanced full stack product engineer. Very good at both web apps, mobile apps, APIs, Postgres, Linux, mentorship, and communication in general. Touch typist, VIM ninja, refactoring monster. With an academic background of philosophy (!)
Mostly startup oriented, developed a lot of projects for different teams and industries (finance, digital marketing, automation, online education, e-commerce).
My specialty is to build simple systems with few moving parts that contain as little accidental complexity as possible. I'm pragmatic but always chase proper implementations at the same time. (See resume for more)
Lately into blockchain (although not an evangelist) and fintech. But open to any kind of projects.
Always looking for interesting & challenging projects and smart people. Open to contract / project-based work & consultancy. Prefer short term work. But I may consider to be a technical co-founder as well, depending on the project.
Remote: Yes
Willing to relocate: Yes
Technologies: Javascript, Python, Node, React, React Native, D3, Postgres, advanced SQL, Linux, Containers, Microservices, Serverless, WebRTC, Ethereum, Cosmos
Résumé/CV: http://gwn.wtf/resume.html
Email: dev at gwn dot wtf
Balanced full stack product engineer. Very good at both web apps, mobile apps, APIs, Postgres, Linux, mentorship, and communication in general. Touch typist, VIM ninja, refactoring monster. With an academic background of philosophy (!)
Mostly startup oriented, developed a lot of projects for different teams and industries (finance, digital marketing, automation, online education, e-commerce).
My specialty is to build simple systems with few moving parts that contain as little accidental complexity as possible. I'm pragmatic but always chase proper implementations at the same time. (See resume for more)
Lately into blockchain (although not an evangelist) and fintech. But open to any kind of projects.
Always looking for interesting & challenging projects and smart people. Open to contract / project-based work & consultancy. Prefer short term work. But I may consider to be a technical co-founder as well, depending on the project.
Remote: Yes
Willing to relocate: Yes
Technologies: Javascript, Python, Node, React, React Native, D3, Postgres, advanced SQL, Linux, Containers, Microservices, Serverless, WebRTC, Ethereum, Cosmos
Résumé/CV: http://gwn.wtf/resume.html
Email: dev at gwn dot wtf
Balanced full stack product engineer. Very good at both web apps, mobile apps, APIs, Postgres, Linux, mentorship, and communication in general. Touch typist, VIM ninja, refactoring monster. With an academic background of philosophy (!)
Mostly startup oriented, developed a lot of projects for different teams and industries (finance, digital marketing, automation, online education, e-commerce).
My specialty is to build simple systems with few moving parts that contain as little accidental complexity as possible. I'm pragmatic but always chase proper implementations at the same time. (See resume for more)
Lately into blockchain (although not an evangelist) and fintech. But open to any kind of projects.
Always looking for interesting & challenging projects and smart people. Open to contract / project-based work & consultancy. May consider to be a technical co-founder as well.
The reason I call touch typing the proper technique is that it does very good in terms of both wpm, accuracy, comfort, teachability and time of mastery. That's why it is more popular than all other nameless techniques. So until there is a technique that does better in all those terms on average, I think it's not the biggest crime to call it "the proper technique". If you don't like it, call it mainstream, popular, whatever.[1] It's the technique every ambitious typist needs to start with at this age (Unless they are already very good). Because as far as I know there is no better technique that is teachable at this time.
As to the guitar comment; there are so many guitar methods. Everybody picks one or another. People who try to learn the thing without help from any techniques / methods won't have high chances of being successful in a reasonable amount of time. (I'm a musician too.) If we agree on the benefit of a technique, when we apply this to typing we naturally come to touch typing. Because as far as I know it is the only documented and teachable typing technique. I'll be happy to be proven wrong. I've been looking for an alternative technique, but couldn't find any until now.
Everybody likes to bash touch typing saying that they have their own special technique they developed over the years that outperform touch typing, but I don't see how this is relevant. We cannot expect everybody to develop their own perfect typing technique over the years when there is already a tried & tested technique available.
In short, what I'm saying is, name a "more proper" technique, and I will shut up. Personal and obscure "techniques" that are not teachable don't count.
[1] And your philosophical argument doesn't really make sense. Yes, touch typing is a human construct. If we can't call it "proper" just because it was invented by humans, then we are in trouble. I didn't call it "proper" because I was implying that it was a gift from the gods. I called it that because there are a lot of indicators that it is the most proper thing that we have available at the moment.
> If you're already fast and accurate enough, you don't need to switch to touch typing.
I agree.
- What makes you call this an "obsession"? There's just a remark and an inquiry. Please point out the obsession part, if you can.
- Ignores which facts? You are responsible with providing at least some of them if you want to be a part of the discussion, do you realize that?
- And what is that reason? The will of the universe?
I certainly wasn't saying everybody should learn touch typing and use Dvorak keyboards. Thank you for the straw man as a bonus.
Read my latest relevant answer that should show that I'm not obsessed with touch typing but have a clear reasoning behind my praisal: https://news.ycombinator.com/item?id=27171906
And if you're going to reply, maybe be a bit more respectful and provide a proper argument instead of empty attacks. I won't engage further otherwise.
> Sure, but I don't agree that touch typing is "the" technique and that it's impossible that someone else has come up with a better one independently. Touch typing is a good way to type well, but I don't think it's distinct from "typing", it's one way to type. Just like you can play the guitar even if you don't know the technique.
I think you have a point here. Touch typing may not be "the" technique. We should always be open to new and better techniques and not embrace touch typing as a dogma, of course. And okay, it's only one way to type, and there are surely other ways to type.
I'm not saying that everybody has to learn touch typing because it was sent by the gods. I'm not even the biggest fan myself. I agree that it has its problems and I know for a fact that there are a lot of people out there with their own techniques who easily outperform touch typists.
So I'm not defending touch typing "at all costs".
I was praising it because I have an educator's perspective here and have the general public in mind, especially when I offer general advice in a forum like this. At the start of this thread I was replying to a person who seemingly didn't know much about touch typing.
While there are reports of other techniques that easily outperform touch typing in terms of wpn, accuracy and comfort; there are other properties of a technique that may or may not be important depending on one's perspective.
Let's call them "teachability" and "time of mastery". Touch typing is a very valuable tool not just because it allows one to perform sufficiently in terms of wpm & accuracy, but also because it is very easy to teach it. One doesn't even need a teacher as it's completely public and straightforward knowledge. There are very clear instructions on how to master it, and the mastery happens in 3-6 months. All very predictable and guaranteed. I don't know of any other technique that is comparable in this regard.
And there are so many people out there who don't know about touch typing or realize how much better it can make their lives. Touch typing is their quickest path to better productivity.
I cannot tell those people that: "There is this established typing technique that you can master in 3 months, but maybe don't learn it, because there are reports that there are people who developed their own better techniques in a couple of years, and there is a possibility that you can end up like them".
Obviously, the expert's and the educator's perspectives are different here, so I don't really think we're in a big disagreement.
But since you are an interesting exception, I'm curious of your take actually. Maybe please offer us some more information:
- Why do you think you did slow down after the switch to touch typing?
- Why did you feel the need to switch to touch typing if the skill you already had was so good?
- Do you think there are any benefits of touch typing over your old technique?
- Do you regret switching to touch typing? Why?
- How many years did it take you to get to 120 wpm at 98%?
- Is there anything you miss from your old technique (beside the higher stats)?
Touch typing is a special technique. Typing and touch typing being distinct things isn't a "way of thinking", it's a clear fact. It's not open to interpretation.
The keyboard is an instrument. Anyone can use it without learning the proper technique, but the technique helps a great deal. That's the whole point.
It is greatly comparable to musical instruments. For instance you can learn how to play the guitar yourself, but if you know the proper technique, you'll have better mastery in a shorter time. This is why it needs to be teached, especially to knowledge workers, who type, type and type all day long.
Maybe the skill you currently have is enough for you, but you shouldn't dismiss the proper technique, especially if you haven't tried it (you sound like you didn't really).
Though if you can answer yes to all the questions below, then you probably don't need the technique:
- Can you easily do 80+ wpm whether it is prose or code?
- Do you have more than 95% accuracy at all times?
- Do you never (no exceptions) look at the keyboard?
These things all make a difference. Having less friction with the input instrument results in a higher stamina in a knowledge worker, which means more productivity per unit of time. Few realize this.