I'm not typically a fan of government intervention in markets but Canada's marketing boards do stop this sort of concentration, so while we have higher average prices we do not get massive swings in prices, nor the physical conditions that come directly out of production consolidation that lead to events (or justifications) like avian flu at the same scale.
I think it's fine if a person (1) recognizes and appreciates the situation, and (2) can make it work without starving to death. There are a million examples of luxury in the first world and we're ignorant of most of them.
Post covid many bike companies were in big financial trouble so new bikes cost less than used, but that's mostly resolved or the companies are just plain failing, so definitely look for a newish (aka few years old) used bike and you'll get a lot more for your money. Manufacturers are all pushing ebikes (with electric motorcycle specs) these days and now 32" wheels (don't get me started - and I'm 6'5") so depending on your planned riding and budget 29" HT or full-suspension mountain bike (off-road, trails, casual), or hybrid style / gravel (light off-road, commuting, touring). Focus on a known brand, quality basics (in the order of (frame, fork, wheels, drivetrain, brakes) and figure it out from there. Avoid cheap versions of ebikes, full suspension or carbon; there's typically good reasons for the price and usually you can't fix or upgrade them - although the Walmart Ozark Trail is a decent attempt (but still has major short-comings; you're better with something like a Polygon HT).
commented directly above this before seeing it. I've always been bike-crazy but over the past ~year ridden A LOT including my first solo international bikepacking trip. My plan is to do something new in the fall but first enjoy a (too short) Canadian summer and riding NFLD => Maine in Sept.
I quit last August for similar reasons, and lest everyone here think it's all amazing ICs vs. clueless managers, I was at the director level of a midsize company caught between the developers I deeply cared for and agentic madness pushed from the executives and my boss the CTO. I'm likely older than many here, but still too poor / young to retire and maybe it was a mistake, but I kind of feel like I didn't have a choice. I've made big contrarian (stupid?) moves before and they've worked out, so we'll see what's next. Over the past 11 months I've explored and worked with AI my way, and ridden a lot of bicycle.
most people are paid as full time salary employees, aka 35-40 hours/week. You may feel that you personally do way more work than everyone else (80%+ plus of people do) but you don't get to define what "the actual amount of work you are paid for" is. There's usually lots of opportunities to find time to learn or go on tangents in non-terrible jobs, but unless your boss is quiet quitting as well, they - and your coworkers - will know, and this will screw you far more in the future than just quiting and getting a new job.
I'll be the person who says what a lot of us believe, and even more know: the internet was cooked when the general public started to use it. The magic, community and naivety were all washed away when the socioeconomic & technical barriers fell, expanding the audience from industry & universities to the entire world. Next came those looking to solely profit and consume; not contribute back. This isn't a new problem just the current loudest version.
Please provide 3 examples where layering on MORE of the offending technology has solved the problem. Spam? Malware & Viruses? Customer Service? Hiring & Recruitment?
>> The developer experience around MSSQL is untouchable.
This may be the case for MS-centric, application & human developers, but I'm not convinced moving forward. Microsoft's BI story is pretty thin and out of date. Postgres has some solid columnar support/functions (which probably why Snowflake is writing about it) which means you can potentially use it for both you transactional and analytical workflows. As more development shifts to agentic workflows I'd bet Postgres shines when the overall ecosystem is more important than the human tools that were essential for the past 20 years. I loved Redgate's value-add but I don't think agents care about the UI which was the big win. SQL Server will continue to live in the enterprise andf where MS can sell lucrative support contracts or build for their clients, but I'm not seeing any net-new projects where the builders have any choice to not use SQL Server.
This feels like the same PE theory / sell job: "Untapped value that can only be unlocked with PMaaS - Professional Management as a Service", only scaled up "because AI". They're trying to change the narative so that SB has a huge intrinsic value, while it's common knowledge that venture funding is a hit-driving business. I don't blame them but it's total bullshit. Funds do this when they're out of ideas and throw a lot of very expensive spaghetti at the wall to see what sticks.
from another perspective - who is better resourced than Google to determine if a person and place are real or fictitious? They make these decisions all the time when it suits them. And explain to me this population who is filing DMCA take-down requests that doesn't have an address? the Venn diagram seems shockingly small.
In Canada WalMart super centers (the ones with groceries) are low quality and have prices as high as (or higher) than other stores. Everything is prepackaged and shipped to the store so meat, dairy and bakery is the worst in town.
I don't think there's some sort of "line" that Delve crossed and Corgi has not, more likely the financial upside for YC wrt Corgi is much, much bigger. They're not going to mess with that even if the screw over a few of their other startups. YC absolutely loves to tout this family dynamic across all their companies and alumni, but there is no way the relationship between a few dozen startups looks anything like that between literally thousands of companies. It's a scaled up tech-hype startup machine now, and has attracted the same MBA-types they supposedly defeated 20+ years ago.
Any long-distance bike ride/race fans here? the Tour Divide just completed and the record was shattered, not by riding for as long as possible, but with detailed planning, a dialed setup and getting a (relatively) lot of sleep & rest. Seems like this approach is applicable to many domains, but it's a lot more work than the obvious approach of "work more".
If this is the scenario, it's no wonder they're underwriting everyone & everything, and can do this competitively, because a broker would need to find either enough new clients and/or efficiencies to justify being the middleman between the customer and the actual insurer. That's typically been the strategy of every financial tech company; I don't see any secret sauce with Corgi beyond "'cause AI!". Move fast and break things is not what I'd want in my insurance company.
that's certainly one alternative, but can we stop looking at everything as a bipartisan scenario with binary outcomes? Maybe there's lots of aspects with mutually aligned interests? Perhaps every single thing in life is not a "us" vs. "them"?
Bingo - the combination of rising interest rates and tanking SaaS valuations has left a lot of these companies - specifically PE funded with mountains of debt - in a very weak position. Funny enough I think small SaaS companies are in a good position, both ownership & their potential use of AI, while larger SaaS companies, are in a lot of trouble. Why rent SaaS when you can build applications with AI? but then, who's going to maintain them?
If you were realigning your SaaS company to ignore your technology short-comings and technical debt, and isntead focus on selling as much "AI-enabled <whatever>" while the rush still looks like gold, this would be a great strategy & announcement.
Maybe they're related by blood, but the apple fell very far from the tree. the ID guys were quite vocal in their dislike of the slow pace & puzzle solving. This was when ID was all about technical advancements and repeatedly making the same game, faster & shinier. They also focused on multiplayer with Quake III arena and Unreal Tournament dictating where the market moved.
At the enterprise level this feels a lot like Snowflake buying StreamLit to try and have a similar experience, and keep you in the Snowflake ecosystem burning credits.
DuckDB kind of created this false comparison by their own early positioning, but I've tried to charitably interpret it as modeling the spirit and motivations of SQLite, not literally being "the SQLite for Analytics". Aside from both being in-process databases they are very different.
compression is a side effect but not really the goal. To simplify, analytical queries often filter on a specific column value, and if these are laid out contiguously it makes disk-level reads much faster than rows that would involve read-skip-read-etc. In transactional systems data is typically written as rows though, so that's likely slower in a columnar system. As a general rule, heavy read workflows with known access patterns is going to benefit from a columnar layout.
the CSV parser is really good too. Anyone who's struggled with consuming CSV/TSV knows this is not trivial. DuckDB uses hueristics to be very liberal in what it accepts without crapping out like many parsers.
the taste that hooked me: the next time you have a bunch of json data, csvs or other data - local or remote - and someone wants some charts (for me it was "productivity" metrics from Jira combined with a bunch of other stuff). First it is very easy/fast to load this data; DuckDB has a very liberal parsing engine and good connectors. Second, I used to worry a lot about my table definitions and cleaning data before structuring it. Not anymore! With DuckDB I find myself iteratively transforming data and creating new tables, combining sources, converting columns, slicing/dicing/rotating. It's very easy to "remix" data and there are functions or extensions for everything you might want to do. There's so little friction to get started that I've found it just naturally becomes the multitool in my toolbox.
THis will give you some experience and you'll start to see applicable problem spaces for DuckDB in product areas, especially anything with BI or DW.