The more we measure, the better we get at separating the false positive cases from the serious ones. Especially in a world where AI plays a bigger role in the development of the medial sciences.
Going forward into the future and not measuring more accurately because we are worried about false positives in our current limited understanding is a very conservative take.
They are quants with a deep experience in trading that started to develop general LLMs as a side business, that does not mean their experience is baked into their models.
I think most comments miss the point on why many small businesses don't have websites:
It's not about it being hard to create and manage a website, it's that the vast majority of customers use social media platforms (as well as platforms like google maps) to find out about shops and F&B. For many businesses having an Instagram page will draw a lot more people than having a random website.
> Here's a thought experiment: Would you feel good if someone read your blog and learned something from it? Probably yes. Would you feel good if they passed along something they learned to others, likely in their own words? Probably yes. What if they couldn't recall, or didn't choose to reference where they saw it? Probably still yes, although (speaking personally) my ego would probably prefer they did credit. What if the reader who passed the learning along was the ai?
This is definitely an interesting way of looking at it. If your blog ends up in pre-training data, it will become part of the AI. Or if not, an AI might still fetch it when a user asks something specific. It reminds me of voting in a democracy, which many people consider a right and a duty - but in reality a single vote is hardly going to swing any election.
> But then I stopped because I had no return from it.
> The main reason was to get back into the habit of writing, and by extension thinking. ChatGPT has weakened my thinking capacity.
I can definitely relate, and find this true as well. While a (monetary) return has never a big focus for me. It's still hard to keep going over time with motivations around self improvement, accountability, etc.
To summarize the current Dutch personal income system: besides income from salary and income from own business (these are taxed quite high), income from investments (stocks, passive investments, real estate excluding your first home) is taxed quite low. The amount is simply a percentage based on the value (as per the start of the year) of your investments.
So in the Dutch tax system there is no difference between realized and unrealized gain. As such it doesn't matter when you buy/sell your investments. It doesn't impact your tax burden. The effect you get is that everyone's wealth just slowly erodes away, just like with inflation (unless your yield outpaces that).
These laws may very well be terrible, but no need to mention on an internet forum you want to help (hire?) someone to mass murder people involved in making them. Jokes and sarcasm don't always land as intended.
As to a more constructive path: bureaucracy all over EU is definitely considered a big problem (for startups, and for many others) and there are a bunch of movements aimed at addressing them at all kinds of levels. For example look at the eu acc movement.
Folkvang is a high frequency, quantitative trading firm active in the cryptocurrency markets. With a backing from Alameda Research, we’ve become a major player in the markets; powered by our fully proprietary technology and infrastructure, we trade billions of dollars a day across a variety of exchanges. We boast a team with years of experience in varied backgrounds and notably developed the open source project, Gekko.
We are looking to expand our team with a full stack developer with a deep understanding of nodejs and experience with quant trading, cryptocurrencies and (cloud) devops.
If you fit the bill, we should talk - please email to [email protected]:
- Your CV or relevant presentation
- Github links (related repos or profile)
Which would get parsed into a BigInt. This specifically means that value isn't a number but a bigint. All JSON consumers that don't support that get strings, all JSON consumers that do get BigInts (when parsing).
The only downside I see is existing json that has strings containing a number and a "n" at the end.
And what if some programmers are put unto fixing this, to realise the normal code path has a number of other bugs for linux? If you write web software you clearly define what you support and what you do not.
I've fallen into the "I know this browser is not supported, but everything works except for X" trap. Where you first spend a month fixing other bugs that also don't work, only to end up with a more complex QA dev process since you need to make sure all new features also work in this other browser or environment.
Going forward into the future and not measuring more accurately because we are worried about false positives in our current limited understanding is a very conservative take.