Hacker Newsnew | past | comments | ask | show | jobs | submit | 9rx's commentslogin

Absolutely. Which is why the hackathon was conceived: to serve as an escape from the real world.

All good things must come to an end, I suppose.


When I first read about the hackathon concept, it was a bunch of OpenBSD developers getting together to work on stuff like cryptography or drivers. I think it was from Facebook where I first heard it as some bullshit corporate event. The idea of a "winner" seems to misunderstand what should be a goal. It's not a competition. It's collaboration.

I’ve always heard of hackathons as being a competition with judges and a winner.

Sounds like you only know the corporate or post-commercialized version, and not the original concept. The entire point of my comment.

> Now that Google is manufacturing answers

There isn't someone at a keyboard typing content. It's still just search, repeating quotes from other websites. The difference is that the algorithms have turned lossy, so the quotes are not always preserved in their original form.


Obviously, I understand that and maybe you shouldn't have cut short the quote from my comment as that demonstrates exactly and precisely what is going on.

i.e.

> Now that Google is manufacturing answers using their own LLM

To be honest, I find it somewhat rude that you select a portion of what I wrote and then criticise it.


Equally obvious is that it doesn't matter what you do or don't understand. Nor does it matter if you find something to be rude. The comments, they are not written for anyone in particular. This is a public forum. Comments are there for all.

Look... its clear you didnt read the article. The point of contention is that google _hallucinated_ facts. As in, website 1 said company A exists and website 2 said company B committed a crime and now googles AI summary says company A committed a crime while linking website 1 and 2.

The court found google to be liable for that, because company A has no other recourse otherwise. Which website operator was the company supposed to contact to remove this "false" information? It only exists in the aether of google search results, and only as a side effect of them adding functionality into that when someone is searching.


Remember, CPI exists to attempt to figure out how the value of a currency has changed over time. It's not a cost of living index, a housing cost index, a wellness index, or anything of the sort. It is not trying to measure how you are doing in life. It is not there to determine the value of labour, the value of housing, the value of food, or the value of anything other than currency. It is simply compiled to determine the difference in value between $1 yesterday and $1 today, so to speak. As you can see, you cannot use the currency itself to provide that measurement. $1 and $1 are visibly the same; except we know that $1 and $1 aren't the same over time. That is where CPI steps in.

If you want to understand something else, use the measures and data that are focused on that something else. Right tool for the job and all that.


Huh? Housing becoming significantly more valuable than in the past[1] does not imply that wages have dropped.

[1] Mostly thanks to computers/software making housing a more compelling proposition. Historically, people couldn't wait to get outside or over to the pub and would allocate their spending to support that, but now that they prefer to stay in to look at screens, they deem that place where they spend time worthy of greater spending instead.


The GFC wasn't good? It wasn't good for the general economy, sure, but given the specific industry we are talking about that was one of the best times ever. Money was being printed hand over fist building software that did nothing more than emit a fart sound. The opportunities for us with the 'picks and shovels' were endless with everyone trying to strike gold at the App Store gold mine.

The iPhone app store mania is not at all representative of the state of industry as a whole. Most software jobs did not look like this, at all.

It is unclear what you mean. It is true that most software jobs were not writing iPhone apps, if that is what you are trying to say, but those were good jobs. Those who didn't have good jobs for a moment were quickly scooped up by investors trying to create the next big app. It was a feeding frenzy out there for tech workers, despite much of the rest of the economy faltering (agriculture also did very well during the GFC, to be fair).

Maybe you are trying to say that there was some grey beard Atari programmer out there who refused to start writing iPhone apps and couldn't find their dream job banging bits on the old 2600? That is likely, but it is equally likely that they never found that job since either.


It took a bit for the VC world to heat up and a lot of big companies had laid people off.

> So yes, there is a significant job crisis.

And the link echoes that there is a job crisis. But not an AI job crisis; rather a COVID frenzy fallout job crisis.


Workers taking on new/different roles isn't the same as being replaced. Workers have been taking on new/different roles since at least the advent of agriculture, so that's nothing new. Being replaced would be something new, but the data doesn't support it.

BLS doesn't look at job ads when compiling "job opening" data. Their method isn't perfect (nothing in life is), but far more comprehensive than you give it credit for.

So what do they look at?

The results of them actually talking to businesses and asking questions that are more than "did you have a job ad posted?" You are hardly the first person to imagine that job ads aren't representative of actual job opportunities. Obviously they are going to put in effort to avoid those weak signals.

How many businesses were surveyed?

As many as was required to find statistical significance. This S in BLS stands for statistics, after all.

What are the flaws in this methodology?

> Whenever you change the structure within that blob, your type checker won't flag that the receiver hasn't been updated to handle it.

The relevant type is "blob". There is no further structure. If the function that accepts void* is trying to extract structure out of the blob, there is a bug in that function and the type checker should already catch you trying to extract structure from something that isn't there.

> I mean WHY are you making an API that takes such a pointer to an unknown type to begin with?

It's not unknown in any meaningful sense. It is known to be a sequence of 'arbitray' datums of a given length, which is the exact type of input required for the scenario given.

As the article explores, some argue that you should define that sequence with a concrete type, but the article states that it doesn't offer any additional value as is posits that void* already communicates the same. In other words, it suggests that void* is the concrete type for that type already.



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

Search: