drenvuk

Replying to state that I'm wrong, mathematically.

made me go on a wikipedia dive. Thanks, I learned something.

straws have two holes. let's say you had a y split straw. does that have one hole or two holes or three?

I have wondered if it's the lack of manipulation and input ability that computers have in comparison to paper that makes it superior. by manipulation I mean right down to being able to crumple the paper, throw it across the room then go and pick it up again to check something.

I use a notebook as well btw, for leetcode as well. it's simple better. limited in it's distractions, requires a greater amount of lingering on thoughts rather than quickly typing in whatever words have come to mind, freedom of input and manipulation. it does one thing slowly, not everything fast and the interaction it requires is beneficial to then thought process.

even tablets are not as good. anyways, I agree with you.

I'd like to ask how you used the notebook. diagrams and drawings? quick notes and thoughts? what was it like and what was your thought process like?

All I hear from you is whining, from the first sentence to the very last.

Either suck it up and utilize your anger and envy as impetus for changing your situation into one that you're satisfied with, detach your own self worth from that of your friends or continue to be a baby and keep crying in your slum.

my mother came from a family of cotton pickers, I got a leg up and my children will be getting an even bigger leg up.

This might seem unnecessarily harsh but crying will get you nowhere.

The reason I chose to measure curse words rather than vocabulary size is that I believed that people with an adequately sized vocabulary would be able to accurately utilize words rather than relying on curse words which are more flexible. To me, curse words seem like easy placeholders for feelings that the speaker or writer isn't willing to take the time to describe.

Testing vocabulary size is similar but penalizes people with a limited but accurate vocabulary, regardless of whether they use curse words as a crutch.

But again, assumptions and flaws, etc, etc.

How would you measure intelligence in something that could be contained in a simple sql query?

Just a simple ratio: curse words/normal words over a period of time. There was some study that said smarter people are more likely to curse or something to that effect but every experience with the smartest people I've come into contact with has shown me otherwise. Their vocabulary, positions in their line of work, logical arguments and grades when we were back in school are what make me think I'm right.

I'm willing to believe I'm wrong again because there could be any number of other factors. But we're talking about outrageous beliefs so here we are.

I was confident that the users of news.ycombinator.com were getting dumber in aggregate. But yesterday I decided that the feeling in the back of my mind had been there long enough so I ran some simplistic data measurement. Turns out that based on my methodology the influx of people "dumber" than those who were here first started between 2011-2013. I was among them. Also the level has been consistent since those years so not much has changed.

I'm going to attempt to get data more often to confirm my assumptions outside of this one circumstance. Seeing my beliefs disproven was a bit of a wake up call. Also, I need to stop being a dick.

I don't really understand why any drawing of the virgin mary could be worth millions regardless of whom it's by. There's so many renditions. At this point it feels like biblical fan art and the Louvre is filled with it.

I'd rather see art that hasn't been repeated ad infinitum like stuff by osman bey or charles curran or something else. I guess it's just taste? I probably don't know anything, just talking.

this happens when you ride along rather than drive the meetings and schedules. if you stay ahead you have control. it's when deadlines become an issue that other people start acting out of line with your predicted work windows.

I have to disagree, they are relevant. SV needs bodies for the various profit grinders and a way to put pressure on other elites. Wastefully discarding somewhat functioning humans isn't ideal.

Then you're a paragon of honesty. There are many others who aren't, sadly. Rather than assume people are liars I use the live coding test more as another filter. It verifies the resume, sure, but it also showcases or sometimes exposes other aspects of the candidate that a resume or maybe just their resume cannot.

This would only be one facet to an interview and definitely not the entire technical portion.

A standardized test might actually be ok but I doubt it could encompass all of the technologies that appear over the years which one would use at a company if the company is looking for a specific skillset. That's why we go with resumes. I would be willing to bet that you have at least one thing on your resume that is embellished ever so slightly. Some people take it a bit further than others, which is what these interviews are meant to ferret out.

Well here's something that may make you feel a bit better about interviewing:

When I'm asking you a technical question, I'm looking at the code you're writing, not you. The camera is only on to make sure you're not lip synching or something. The layout of your code and the logic that went into it is more important than your mannerisms.

I refuse takehomes on principle because I've had enough bad experiences with poor reviewers so I'll never give one out.

What? What would you rather have? A takehome? People find a reason to complain about those as well because the ones administering them become really god damned nitpicky.

What I try to give is a three parter simple string parsing manipulation question where you build on each successive part as well as providing both valid and invalid inputs for them to use as test cases. It shows organizational skills and the ability to break down problems into reusable parts as well as the super basics of string parsing. I think being able to do that much under time pressure shows the learned qualities of a programmer since most will go with what's been ingrained into them by way of habit.

I can understand brain teasers being a poor measure of ability but I'm super on board for online whiteboarding when done properly. 45 minutes, no muss, no fuss. No 6 hours on a weekend to make something. No impenetrable question that requires tricks you don't need for day to day work that you can later look up.

Zero, despite trying to change it. Reams and reams of code to the point I feel like my eyes have burn in but no books. I'm not sure if this needs to change.

nfts are just as bad as copyrights. both require unnatural systems in order to exist. both attempt to reduce freedom of speech and the proliferation of ideas. both need to be removed.

I'm not sure if you feel attacked or not but you shouldn't. Being lazy is good for programming I think. You should keep in mind that your functional programming base is built on a figurative 10 billion layers of abstraction already. It's just that those abstractions are somewhat well made so you don't have to think about it.

Proper abstractions aid in understanding and can ideally be optimized away. Poor abstractions hinder it and slow things down.

I would.

Instead of properly managing mutable state (which can be difficult in situations with growing teams and complex application logic) people are opting to just copy everything or copy a subset of the tree they need so they don't have to think about it.

Immutability is bad for performance when the purpose is not recalculating a certain state after a certain number of operations(memoization). Many of the best practices that have cropped up in the past few years has been more for helping teams of people deal with growing code bases rather than helping programmers deal with limited hardware. In computer science this should be self explanatory. For optimal runtimes the act of making copies is avoided. Why people usually seem to ignore the fact that they're wasting cycles for the sake of the holy grail of clean, functional programming and immutability has eluded me.

Typescript, focus on immutability, microservices even. I hate all of them but they have their purposes. They solve people problems. Maximizing hardware performance is not in the list though.

I wonder why they don't mention dexie with all of the other options. Like they say, batched operations solves this handily and Dexie has great support for them and it's really darn fast.

“Ah you think darkness is your ally? You merely adopted the dark. I was born in it, molded by it. I didn't see the light until I was already a man"

Sorry for this, but I find the parallels a bit funny.

So now we have to trust their recommendation algos rather than other users to avoid trash content. This is stupid.

Tried it for a week, didn't like it. Utility classes vs compile time css in js + styled components are better in every way when you actually know css.

>But, preventing global CSS removes the expressive power of the “cascading” part of Cascading Style Sheets (CSS).

lol wat? variables exist and import exists if you wanted to stick with style.module.css. StyledComponents works very nicely for this as well.

    <div class='text-base font-sans font-medium rounded-lg bg-gray-100 text-black py-3 text-center cursor-pointer'>Button</div>

The above line of markup looks like utter crap tbh, not to mention, the fact that it's a div vs the name of what you consider it to be in the context of the other objects on the page seems like you're obfuscating its role. I just don't think it's a good thing to use unless you're doing a bunch of one offs that you'll never have to support.

Maybe one week isn't long enough. I dunno.

/all was opt in. this is basically barrens chat from literal decades ago. I feel like things turned out ok back then. What's the difference now?

first thing I wonder is whether it's a stimulant or not.

How is mocking services impractical? You have to do it anyway for tests.

How is having their source code impractical? You should have downloaded it anyway.

The only one that might seem extreme is downloading the SO dbs. I have done this because I stay offline so I can better focus. Not everyone (probably very few) will reach that point.

I think you're overblowing how recent the information you require is tbh. You can get a lot done with months old information.

1. Of course you need the internet if you're hitting an api but the docs will get you to the point you can test it yourself without internet access by mocking their services.

2. If you're using a new framework or plugin you should have the source available in addition to the documentation. That should tell you all you need. 10 month "dusty" documentation means you're working with unstable code. If you don't have the source to inspect then you have other issues, the first being the proprietary code inflicted mess that you have to deal with.

3. You can download the stackoverflow databases of the topics you deem important and search through them.

My bet is that you haven't really even tried.