Series would be perfectly fine, though out of context it might be a bit confusing because it's also used to describe data on a chart.
Using the singular "Sequence" might also be appropriate for a component name, as the component represents the collection entity, rather than referring directly to the things within the collection itself (which I presume are either a prop or the children of the component).
A police officer would. The penalty for an accident might be negligent driving.
The penalty for an accident without a license is, at minimum, driving without a license. You're also not likely to be covered by insurance without one either, even if you're not at fault.
Take a person who has marginally acceptable eyesight, who never drives, put them in an emergency situation where they need to drive and you've got a recipe for much higher odds of having an accident.
Given that getting a license is an option, and it conveniently doubles as a photo ID, and there's really not a reason to not get one.
What the fuck are you talking about? My mother didn't laugh at a joke because Jesus was in it. That's the kind of adherence that leads to hurting people because they disagree with you. Religion is stupid, it hurts people.
If my memories serves me right it was meant to be "Copy Convert" but "cc" was already taken for "C Compiler" so they went to the next letter in the alphabet (alpha beta), hence "dd". Thanks for listening to my TED talk of useless and probably false information :)
According to Dennis Ritchie, the name is an allusion to the DD statement found in IBM's Job Control Language (JCL), where DD is short for data definition https://en.wikipedia.org/wiki/Dd_%28Unix%29#History
An asphalt roofing shingle company just closed in Minneapolis due to the city's new CO2 tax. The local environmental group held a little press conference crowing about it.
Mind you, this won't change the demand for asphalt shingles, they'll just be shipped from further, generating more C02 on the whole.
The only other current alternatives are all non-renewable as well- mined clay, slate, or metal. For residential roofs, I'm hoping metal continues to come down in price, as they tend to last longer and can be made to look quite good. For commercial / flat roofed buildings, there still needs to be some very thick rubberized underlayment below gravel or whatever to prevent standing water from getting in. The same is true for sod roofs in hobbit style earth homes.
So, yeah, there's still people in power who expect that all petroleum based products are equally evil and must be punished.
> An asphalt roofing shingle company just closed in Minneapolis due to the city's new CO2 tax. The local environmental group held a little press conference crowing about it.
For what it’s worth, Owens Corning operates an asphalt shingle plant in North Minneapolis (1701 49th Ave N) and they have no intentions of closing it down.
That's nice, but my response was to demonstrate that there are in fact people who think there's post petroleum industry, or at least desire it, not that none are foolish enough to stick around.
The original tax passed by the council, and overriding the mayor's veto was 90 times the current one at $452 a ton versus the current $5. The only reason for the drop was that the original couldn't possibly survive a challenge in court.
The environmental group celebrating the GAF closure is also real, and would likely celebrate Owens closing too.
Having participated in the build of an inventory system / system of record for a large national retail company, I can't see vibe coding helping anything more than the prototyping in the discovery / requirements gathering parts of the process.
The sheer volume of data, the need for real time consistency in store locations, yada yada means that bad early decisions bite hard down the road.
Lots of drudge work can be assisted by AI, especially if you need to do things like in ingest excel sheets or spit out reports, but I would run far away from anything vibe coded as hard as possible.
One of my clients spends 500k+ on XXX licensing per year (for a 200M revenue company that's not peanuts), and on top of that has to employ 12 full time XXX developers (that command high figures just for their expertise on that software while providing very little productivity) and every single feature takes months to develop anyway. Talking about stuff like adding few fields to a csv output.
So the total cost of XXX is in the 2M/year range, and it keeps ballooning.
My (4 men) team already takes care of the entire warehouse management process except inventory, the only thing that XXX provides, we literally handle everything: picking, manufacturing, packaging, shipping phase and many others.
In any case, nobody has mentioned vibe coding.
I stated that a handful of good engineers with the aid of AI in a couple of months can provide a working prototype to evaluate. In our case it's about extending our software that already does everything, except inventory management.
When you spend 2M/year on a software (1% of your revenue), growing every year by 100/150k it makes sense to experiment building a solution in house.
That situation makes sense but then i have to ask why hasn't it been done already? Software developers are not rare and if the use case is so isolated and discreet then surely it would have been tried by now. Even without genAI, CRUD, RDBMS record management, SSO, row level security... none of those things are new or out of reach until now. I think what you'll find is when you sit down with the users and start asking about the parts of the exiting system they actually need you'll never get agreement nor a clear answer. When/if you finally get a set of requirements and after UAT sign-off and then after go-live the users will say "this isn't what i meant" and you're back to square one. Rinse/repeat for years and then one day an exec will say "why are we wasting all this time, let's just subscribe to an OTS saas and make them configure it to meet our needs".
Nobody gets fired for choosing SAP, Salesforce etc.
Spending tons of money to get a janky, unreliable system of record, or finding out too late it is missing crucial auditing capabilities, or that it has Big Money bugs, on the other hand, is far worse, especially if you have investors asking what the hell you were thinking.
Your point about users not knowing what they wanted until after the fact is also painfully true. The hardest part about these systems is the people most likely to buy are the ones who have been doing it with a lot of human processes for years. Buying a SaaS or other third party product means having leverage to force them to change to more standard practices. Building in-house means that everyone will fight to high hell to make sure that their special snowflake way of doing things is accounted for and you end up in a worse spot as a result.
Its funny you mention excel, I see vibe coding in the business sense right now being a gateway to replace all of the ad hoc uses of excel. We've basically leveled up the quality of the software you can build before buying a SaaS product or a hiring an in house engineer.
It was 2020 and they were using a format that was replaced in 2007.
It. says more about their issues than Excel. I doubt paper forms would have saved them. Maybe they'll run out of paper and just ignore new entries too.
The moment vibecoded excel has a bug that regular Excel doesn't and a user has to wait on you to re-vibecode it's over. They'll just use Excel while you're trying to get the llm to find and fix the bug.
Your brain doesn't need to indulge in sugar to the point of becoming a poisonous vice. You can get more than a sufficient amount eating readily available whole foods.
It's a bit like suggesting we are all addicted to water. Sure, enough of it will kill you, but that's not exactly helpful pedantry.
> The old rules of reputation and shame are gone. The door is open to people who will generate and spam bad PRs and have nothing to lose from it.
The important part here is that reputation creates an incentive to be conscious of what you're submitting in the first place, not that it grants you some free pass from review.
There's been an unfortunate uptick in people submitting garbage they spent no time on and then whining about feedback because they trust what the AI put together more than their own skills and don't think it could be wrong.
Wikipedia has much better information about guns than most of the people talking about them in politics, generally speaking.
It's not too surprising, considering the way the rules are written at the ATF. There's basically zero logical thought that goes into pistol vs rifle vs felony:
ATF rulemaking can be unintuitive and arbitrary but there really is a level below it occupied by people who have dedicated a significant chunk of their lives to trying to restrict firearm ownership, who genuinely seem to believe that Die Hard, Rambo, and Spaghetti Westerns are real life. Politicians who can't answer basic questions about their legislation, who have to be told live on air that magazines can be repacked, that just make up impossible crime statistics. Yeah it's stupid that the ATF has decided that vertical grips are a rifle feature but angled grips aren't, but it gets worse.
There's no legal definition per Congress. Generally speaking, braces are intended to stabilize a pistol against your arm [0], whereas a rifle stock is meant to stabilize against your shoulder. However, braces can technically be "misused" such that the rear of the brace fits against the shoulder, meaning it is used as a stock. Likewise, the distinction is so small something as simple as a sling attachment to the stock could make it a brace, or an articulation that could be used as a cheek rest turn a brace into a stock, converting a pistol into a rifle or vice versa.
For awhile, the only way to know the difference was for the manufacturer to submit an NFA and hope.
The ATF has been in court (and lost) quite a bit [1] over this.
A "pistol brace" is designed and "intended" to be braced against your forearm to stabilize the "pistol" in a way that allows you to shoot a particularly large and heavy "pistol" with one hand. The ATF said this was fine, although I think they really regret that now.
Stock goes against the shoulder. Brace goes against the elbowpit. If you let the brace touch your shoulder, your braced pistol suddenly becomes an unregistered SBR, and you become a felon. Oopsie!
reply