HN user

creativeSlumber

299 karma
Posts0
Comments77
View on HN
No posts found.

it's not important for a CEO to be good with software engineering

If you are the CEO of a company, you should have expertise in whatever your company does, and If your company is primarily a software company, then you should have expertise in software engineering. You cannot effectively manage something that you don't understand.

did anyone on the team really not push back?

This is the real question. If they are serious about not doing something like this again, they NEED to look at what process failed and let something like this get proposed, designed, implemented and pushed to production. Usually things get reviewed at each stage. Did the people who pushed back on this get steam rolled? If no one pushed back, that's an even serious culture question and the entire org would need training.

A serious "we won't do it again", needs to be accompanied by a COE on this for identifying what went wrong, and identifying what guardrails can be put in place and then actually implementing them.

Layoffs at Block 5 months ago

Owning the decision

Owning a decision means you have something at stake if things go wrong. What would happen to Jack if this decision turns out to be wrong? Any consequences?

Layoffs at Block 5 months ago

I've worked at companies that are literally 10x more effective than other competitors in the market purely due to good engineering practices.

Most big tech companies get taken over by leadership with no tech background eventually and the engineering bar drops to the floor.

Are the model weights burned into the silicon / part of the architecture? Or can you update the model weights on these chips? If they cannot be updated, these chips will be outdated the moment they are made given the breakneck speed at which new and improved models are introduced.

Comparing it to X flights maybe correct from a greenhouse emissions standpoint, but extremely misleading from a safety perspective. A jet emits that co2 spread over tens of thousands of miles. The problem here is it all pooled in one location.

Also that statement of 70 meters seem very off, looking at the size of the building. What leads to suffocation is the inability to remove co2 from your body rather than lack of oxygen, and thus can be life threatening even at 4% concentration. It should impact a much much larger area.

what happens if that large enclosure fails and the CO2 freely flows outside?

That enclosure has a huge volume - area the size of several football fields, and at least 15 stories high. The article says it holds 2k tons of co2, which is ~1,000,000 cubic meters in volume.

CO2 is denser than air will pool closer to the ground, and will suffocate anyone in the area.

See https://en.wikipedia.org/wiki/Lake_Nyos_disaster

Edit: It holds 2k tons, not 20K tons.

Many of the dependencies used names that are known to be “hallucinated” by AI chatbots. Developers frequently query these bots for the names of dependencies they need. LLM developers and researchers have yet to understand the precise cause of hallucinations or how to build models that don’t make mistakes. After discovering hallucinated dependency names, PhantomRaven uses them in the malicious packages downloaded from their site.

I found it very interesting that they used common AI hallucinated package names.

to prevent wasted processing.

If that was the case, the message should be about a limit on re-enabling the feature n times, not about turning it off.

Also the if they are concerned about processing costs, the default for this should be off, NOT on. The default should for any feature like this that use customers personal data should be OFF for any company that respects their customers privacy.

You are trying to reach really far out to find a plausible

This behavior tallies up with other things MS have been trying to do recently to gather as much personal data as possible from users to feed their AI efforts.

Their spokes person also avoided answering why they are doing this.

On the other hand, you comment seem to be trying to reach really far trying to find portray this as normal behavior.

I would have disagreed with you in the past by saying, "until it breaks something critical and you loose customers and business", but then again people just moved on from the Crowdstrike incident like business as usual.If something like that which grounded critical service globally and had an estimated 10 Billion Dollar economic impact doesn't change mindsets,I don't know what will.

Pro pricing is $7.25 per active user per month

This pricing model makes no sense for a non-profit that is trying to teach coding to teenagers worldwide. They will have a lot of users (remember) who might only send one or two messages once in a while. having to pay $7.25, for some who just asked a single question, is essentially extortion for a non profit like that who's primary purpose involves reaching out to as many people a possible.

then I think that means they have over 2,000 active members in their Slack which does not sound like a "small nonprofit" to me.

those are not employees, but most likely the people they are trying to help.

Is it... time for me to take another pass at this?

Yes please. I was very excited for Sandstorm when it first started. Sad to see it's current stage.

Also I think the world around has evolved quite a bit wrt containerization from when Sandstorm first started. I wonder how you would build it today, if you were to build from scratch. Could you utilize docker for most of the containerization?

I don't know why the parent post is being down voted. I think it makes a solid argument about creating a car that normal people can afford.

That is exactly what Chinese car companies is doing. Here's a video by Caresoft of the BYD Seagull which s apparently sub $12k. (Caresoft AFAIK do professional level car teardown reports for the auto industry) https://www.youtube.com/watch?v=izvdO-zdlKg&t=2s

I'd love to buy something like that at that price point.

The most mechanical innovation we saw was a new type of brake for EVs. Although Mercedes says that EVs typically use regenerative braking for 98 percent of their decelerations, they still need friction brakes for that last 2 percent—which tend to be critical needs. The reason is simple: typical EV regen can provide a maximum of 290 kW of braking power, while a maximum 1G plus stop might require 2200 kW.

But because these friction brakes are not used much, their rotors tend to rust, leading to noise during application, as well as degraded appearance. And they still produce brake dust.

To solve these problems, Mercedes is developing what it calls In-Drive Brakes. The idea is to move the brakes from the wheels to inside the electric drive motor at either end, where the half-shafts emerge. The prototype is shown on the rear axle, but the concept could work at both ends.

The brake would not be a conventional disc brake but rather something that looks like the clutch in a manual transmission. There would be a disc that spun with the half-shaft connected to each wheel. This disc would have friction material on most of each side near the periphery and with something that looked like a non-rotating flywheel on each side. An annular hydraulic cylinder would press the assembly together causing the rotating friction disc to drag on the two fixed plates to slow the car.

Since this assembly would be fully enclosed in a housing at each end of the motor housing, the two fixed plates would have liquid cooling passages to remove the heat generated by the braking. A small sump at the base of each brake housing would serve to collect the brake dust generated. mercedes benz innovations future technologies 2024, in drive brake Mercedes-Benz

The goal would be for these brakes to last for the life of the car. Being enclosed, they would be quiet. And being inboard, they would leave the wheels clean, reduce unsprung weight, and allow greater freedom for wheel designers, who would no longer have to worry about getting cooling air into the brakes.

This is NOT an innovation. The initial mentioned problem of brake discs possibly rusting because they are rarely used can be easily address by the car computer periodically using the disc brakes rather than regenerative brakes if those haven't been used recently. Applying the disc brakes a few times every couple of days should not impact the range measurably.

They are making an easily reparable wear item such as brakes, almost cost prohibitive (labor costs) to replace by putting it inside depths of the electric drive unit. You now have to disable and disconnect high voltage battery , pullout the electric motor (usually include the motor, differential gear units, inverters in the same unit so it is similar to pulling out an engine in a ICE car), then take apart that engine, replace the friction clutches used for breaking, and then reverse the whole process to put it all back together.

The only thing this is designed to do is to sell more cars every x years by making cars harder to repair. The funny sad thing is; this is clear anti-consumer activity ironically developed with consumers (tax payers) money using tax write-off for R&D.

This type of thing is also why electric cars have a bad reputation at the moment. They depreciate so fast because the the greedy companies design them to make it impossible to repair economically, and insurance companies write them off after the tiniest accident/issue.