HereBeBeasties

No, it's not long enough. You need long enough for the initial investors to get past their lock-up period and either sell their shares, or not, which is typically 90-180 days. Otherwise, index fund investors will pick this up at basically peak overvalued initial pricing, only to potentially take a bath on it three months later.

Additionally with SpaceX they are issuing only a very small percentage of stock compared to a usual IPO, with an unprecedented valuation. Couple that with a much larger than usual amount of the IPO being issued through retail investment platforms rather than to professional institutions (30% rather than a more typical 5%) and it looks pretty unsettling.

I'd have loved to buy a MacBook instead, but the price gouging on RAM and SSD at the time was insane (less so six months later) - massively cheaper to buy a DIY framework and put your own RAM and SSD in.

Does it run the fans hard even when not chewing CPU? Sounds like perhaps a thermal issue - there are guides on repasting/padding heatsinks online; you might want to try that.

Such a thing exists. It's called a Dacia Duster. Well, certainly for utility and to a lesser extent economy.

fibery.io - it is excellent. You need to configure it, although it has various templates to get you going out of the box, including sprint-based development.

The nice thing about it is that you can add whatever you like, however you like. Want components with default owners for tasks? Want milestones? Want stakeholders? Want sign-off reviewers? Want to integrate with existing tools like Linear or Notion or JIRA or even email inboxes or Slack messages? Add entities for Incidents, that automatically make a dedicated Slack channel when you create them?

Want proper 1:1 or 1:manu or many:many links between Tasks and Milestones and Sprints and Incidents and Teams and Components and whatever?

Want single assignees? Or multiple ones?

Want flexible custom reports on all of it?

Or just want a simple flat Todo list, that can evolve later to fit your needs?

Stop having the tools dictate to you how you work and instead set it up how your company actually wants to work. That's Fibery.

(I am not connected to the company, just a very happy user.)

It seems that the person who did this acted unilaterally, with no code review, and ignored (then disabled) broken tests while landing this (https://github.com/pypa/setuptools/pull/4909). One should not be too harsh - he seems to be a student. One perhaps should be more harsh on the commerical entity sponsoring the project, though - setuptools is sponsored by Sonar via "Tidelift". According to https://tidelift.com/subscription/pkg/pypi-setuptools:

> The maintainers of setuptools get paid by Tidelift to

> implement industry-leading secure software development

> practices and document the practices they follow.

Well, that really doesn't seem so in this case now, does it?

Fibery is the answer. It's absolutely great: https://fibery.io/

Honestly, all you lot complaining about the speed of 286s or 386s!

I have fond memories of implementing a Mandelbrot set renderer on a CASIO fx-7000G graphics calculator. 422 bytes of programmable memory! The TI-93 I did it on later was considerably faster and easier to make it fit in. :-)

fibery.io all day long :-)

It now has a thread view so you can replace tools like Slack with it, and entity-grouped notifications, so you can easily catch up on things if you are away for a few days. Plus it does a much better job of proper knowledge management, with references, proper relations, build a domain model of your business, per-entity and linked-entity permission models if you need that, etc. etc.

It provides integrations for existing tools, so migrating to it is much less big bang (sync in your JIRA tickets, Linear, Slack conversations, etc.).

Two-panel nested views on entities make navigating through status on task boards, projects, etc. a joy. You can build automations (create a new Slack channel and invite the assignees to it when I make an Incident, add a 'priority' labels when certain people comment or certain keywords are used", etc.).

Add meeting minutes, automatically convert the follow-up bullet points in those into Tasks for people and assign them, without ever leaving the same single page view.

You can use it a bit like e-mail, and a bit like JIRA, and a bit like Slack. And you can pick and choose those "bit like"s to best fit your needs.

We haven't completely replaced Slack with Fibery, but we've moved most of our more intentional communication into it. We no longer feel we need to "complete Slack" to catch up on the state of the world.

We love Fibery and are very happy customers. ♥ It's great.

Employer tax contributions

Office space

Hardware and software, SaaS licensing, cloud costs, etc.

Hiring costs (recruitment, recruiters, time lost in selection and hiring)

Secondary cost to rest of the business to change processes, retrain, integrate, help the dev team understand requirements, effectively build and iterate, etc.

Quite possibly a bunch of compliance, security, audit, pen testing, and other regulatory costs depending on the demands their clients have, etc.

Running a team != hiring a bunch of freelancers as a one-off.

List of actual affected devices - https://github.com/binarly-io/SupplyChainAttacks/blob/main/P...

No, I'm not surprised either. But if you're operating at this kind of scale and with this level of immediate roll-out, what I would expect are:

* A staggered process for the roll-out, so that machines that are updated check-in with some metrics that say "this new version is OK" (aka "canary deployment") and that the update is paused/rolled back if not.

* Basic smoke testing of the files before they're pushed to any customers

* Validation that the file is OK before accepting an update (via a checksum or whatever, matched against the "this update works" automated test checksums)

* Fuzz tests that broken files don't brick the machine

Literally any of the above would have saved millions and millions of dollars today.

https://opensource.com/article/20/4/plot-data-python gives some common options. What kind of plots are you trying to achieve? Interactive? Jupyter notebooks? Reporting? SVG or HTML output? You might also like to look at things like https://evidence.dev

Lay-offs aren't necessarily a sign of failure or bad strategy, so your logic does not compute.

Lay-offs happen for all sorts of reasons. It may be very reasonable to have X number of people one year, but changed market conditions, or financing rates, or whatever else mean it no longer does the next year.

People don't have magic crystal balls. But even if they did, it may still make sense to hire people while financing such a thing is cheap, and to lay those same people off when it isn't any more. Make hay while the sun shines, and all that.

You may not like the fact, but getting rid of poor performers makes businesses stronger and better. Rounds of lay-offs undeniably make such decisions easier to make and justify in large companies.

CEOs who do the same (or more) with fewer resources are generally rewarded. As a shareholder in the company you'd want them to do more with less and make you more value, right?

You might as well argue that any CEO who needs to hire more people has failed. That sounds obviously silly, but it's genuinely an almost equivalent argument.

All of this may not be pleasant for those involved and especially those who are losing their jobs, but that's capitalism for you. Big business doesn't tend to optimise for people's feelings - it cares more about the bottom line and being competitive.

In this case there is an obvious and pressing need. The streaming music scene may be a tremendously complex place to operate a business in, with all it's licensing and labels and countless jurisdictions and legal complexities, but both Apple and Google are sitting there ready to eat Spotify's lunch if they can't figure out profitability.

Glassdoor numbers will be gross of income tax, but not include employer social security contributions, which is 31.24% on top of what you see as listed gross salaries. That is his point.

Don't forget if you're doing back-of-the-envelope stuff that there is also 20.6% corporate tax on revenue that has originated in Sweden. And companies resident in Sweden are taxed on their worldwide income, although if they are taxed elsewhere then this elsewhere amount can be deducted. But this means you are paying at least that amount. I imagine some chunk of Spotify's workforce exists to optimise and figure out all of that, given the number of legislatures and tax environments they have subscribers in.

That's not a phone AND she is using a stylus.

As a previous GitHub Enterprise Server customer on a site with hundreds of users, who's spoken with a number of GitHub employees about this, I do not think that is true. They would far rather you were on GitHub Enterprise Cloud. They view Server instances as a necessary evil for people who have compliance or security requirements they can't handle with the Cloud version, but it is fairly obviously a pain in the neck for support, and attempting to attain feature parity. They have been trying to bring their Server offering closer in architecture to the Cloud version since forever (e.g. moving to Nomad a few years ago to orchestrate it all as containers, so you can shard the services out over multiple hosts similar to github.com, etc.).

I am in management. I evaluated most of the on-duty tools that are available, at the cost of a couple of days of my personal time. At least they all have free trials. PageDuty, Opsgenie, Splunk On-Call (ex VictorOps), AlertOps, Squadcast, TaskCall, etc. etc.

They are all surprisingly hopeless. For example, none of them have SCIM integration to make managing your teams in them automatic. All of them have clunky calendar overrides. None of them seem to integrate well with Outlook / Google Calendar, particularly none take into account holidays. Many have no Terraform provider to manage them, and the ones that do are clunky at best, and hard to set-up/manage. OIDC is hit-and-miss. For example, for PagerDuty you need to call up their support team and get them to manually tweak something that's not in the UI settings to get OIDC for Azure AD sign-ins to work.

It's not that management is apathetic. We genuinely don't want to engineers spending their time working around vendor inadequacies and lashing this stuff together with barely-maintained scripting that they resent having to write in the first place. Why would anyone want that? Given there's seemingly no product out there that lets you avoid that, what should we do? When they're all rubbish, you either choose PagerDuty because everyone does, or Opsgenie as a protest vote, because at least both have Terraform providers and plug-ins for other things like Slack and Sentry, etc.

Harry begs to differ: https://www.youtube.com/watch?v=ezmeX8c672U - it's 2.3 tonnes for the M50, which compromises all the dynamics quite considerably. He absolutely slates it in that regard. Regarding range "A range of under 200 miles is simply not good enough, especially at eighty thousands pounds. I would just buy the Tesla instead of this. The first real disappointment of 2022."

https://evcompare.io claims a real-world winter range in miles of:

192 for the BMW i4 M50

241 for the BMW i4 eDrive40

252 for the Tesla Model 3 Performance

282 for the Tesla Model 3 Long Range

So yes, the much slower i4 with the 18" wheels gets a similar range to the much faster Model 3 Performance with the 20" wheels. That's not really apples-for-apples though is it?

If you don't want the M50 / M3 Performance speed, then save the £6k and get a Model 3 Long Range. You'd have more performance and more range than the i4 eDrive40, and a car that weighs nearly half a tonne less.

(That's before options - it's about £9k to get all the things that are standard on the Tesla, like keyless entry, a heated steering wheel, electric seats, lumbar support adjustment, auto-dipping headlights, wireless phone charging, drive recorder, active cruise + lane keeping (autopilot), a glass roof, etc.)

I don't know about the US, but here in the UK an ID.4 GTX is £55k if you want a heat pump and not in flat primer grey.

A Model Y long range which is faster (by 1.4s to 60mph) and has better range is £2k cheaper.

That's quite a lot of projection. I bought a Model 3 because it felt objectively better / better value than everything else on the market at the time, having, you know, actually test driven pretty much everything. (Kia EV6, Hyundai Ioniq 5, Kia e-Niro, Jaguar I-PACE, Porsche Taycan even).

Techies might (gross generalisation warning) tend to: a) Have higher than average disposable income b) Be early adopters of new tech c) Care less what other people think of them than an average person d) Judge things more objectively than an average person.

So it's hardly surprising a lot of them end up buying a Tesla Model 3. They are very well-packaged, fast, have good range, the Supercharger network, and are fairly mid-priced as cars these days go (similar to say a slower BMW 3 series diesel, at least in the UK).

The BMW i4 launched recently. The Tesla Model 3 is a six year old design. And yet the i4 has much worse range, is either slower or much more expensive, and according to all the critics seems to be less fun to drive.

Heaven forfend that anyone buy a car on its merits, as opposed to what other people think of the badge.

I honestly don't wish to do the original poster down, but has anyone actually found code visualisation things like this (graph or otherwise) useful, as opposed to just pretty?

It seems like you would only really have need for visualisation if your codebase is complex enough. And if it is complex enough, visualising it is generally something of a mess.

What actionable insights can be generated? Has anyone changed anything as a result of such a visualisation?

It always feels to me like you're better off figuring out which modules you have shouldn't depend on certain other modules and finding only those links. Which is often best done with a simple ripgrep, no?

Twingate is missing from this list. It has nice DNS-based routing and access control.

If you're on Android, Microsoft Authenticator shows accounts that are registered with the Android system. To remove one, in Android itself go to Settings / Passwords & accounts.

What if I stop the car entirely while I perform the adjustments? "Put it in park" I hear you say. Tedious, and doesn't always work anyway - many cars leave you with a full-screen reversing camera even once you're moving forwards until you get above 5mph or whatever. And what if I want to stop and adjust my side mirrors to see better, and those are adjusted via the touch screen? (I'm looking at you, Tesla.)

Guess what? I can happily reach down and adjust a real temperature dial by touch while looking at a reversing camera, without looking at that dial or being distracted, in the same way that I can do that while driving forwards. It's the touch screen that's the problem here.

That is only the case if the consumption rate is fixed. If the rate of consumption is adjusted in a feedback loop based on queue depth and/or latency then clearly you can keep your queues in a balance of being neither empty nor infinite.

As ever, it depends on your use case. If you're rendering 20 TODO items then who cares?

If you're rendering thousands of items on an SVG data visualisation, sure it matters.

You can tell it matters because otherwise React wouldn't have implemented escape valves to improve performance, like shouldComponentUpdate.

You can get around this by using persistent data structures with lenses, which is how Elm works. Then it's just reference equality checks as you go down the tree, which is inherently faster.

The Matrix talk is very engaging and full of live demos and cool stuff (seamless failover of your chat to bluetooth low energy comms anyone?) https://fosdem.org/2023/schedule/event/matrix20/

In normal English usage, a quantum leap is a step-change, a near-discrete rather than continuous improvement, a large singular advance.

Given we are not talking about state changes in electrons, there is nothing wrong with this description of ChatGPT - it truly does feel like a massive advance to anyone who has even cursorily played with it.

For example, you can ask it questions like "Who was born first, Margaret Thatcher or George Bush?" and "Who was born first, Tony Blair or George Bush?" and in each instance it infers which George Bush you are talking about.

I honestly couldn't imagine something like this being this good only three years ago.

When I cross the road I mainly use my eyes, so I should ignore my ears if they hear a car coming because that signal should not be needed.

I normally spot fire with my eyes by seeing the smoke, so if I'm lying in bed at night and I smell burning, I should simply ignore it because that signal should not be needed.