• 0 Posts
  • 655 Comments
Joined 11 months ago
cake
Cake day: December 6th, 2024

help-circle


  • I personally know a person who was charged and convicted of the Crime of Libel (in what for my country was an incredibly speedy legal process) for accusing a local politician of Corruption.

    Curiously, about a decade later said politician was convicted for Corruption. Lets just say it only happened because that Libel conviction really pissed of that person who had time, brains and no fear of their professional life being affected, so they worked tirelessly behind the curtains to push an earlier report into “irregularities” in his City Hall all the way into and as a case against him, including digging evidence even from abroad and having to threaten with exposure in the Press at least 3 public prosecutors who on different occasions were quietly holding the case so that it didn’t get to court before the deadlines for prosecution expired (and even then that politician actually got away with a number of crimes because the deadlines for prosecution did expired for those). In fact that was the first politician ever in my country convicted of Corruption.

    Libel having been made a Crime in my country (which is quite unusual in the World) was done exactly so that people can be punished for openly accusing the powerful of malfeasance without the powerful having to bare the costs for a civil court case and actually prove damages (so it mainly helps politicians in the big parties who have the connections to get the local Public Prosecutions Office to take the case to court) and that’s exactly how it has been used.

    By an amazing coincidence my country is one of the most corrupt countries in Europe and last I checked was the one most behind in implementing the EU advised anti-Corruption measures.


  • Well, for merely commissioners that moved from the commission to those positions, the first example that comes to my mind is the head of the EU Commission during the 2008 Crash and it’s aftermath, who went to Goldman Sachs afterwards and is still there today as a non-executive president.

    During his time in the Commission they were very pro-Finance in the way they handled the aftermath of the Crash with him personally pushing frequently for measures were EU money was used to unconditionally helped the interests of large Financial Industry companies, and Goldman Sachs is one of the largest companies and massively benefited from, amongst other things, near-defaulting Greek Treasuries being bought from the private sector by the EU, which subsequently forced the Greeks into Austerity to as much as possible pay those Treasuries.

    There’s even a scandal with him were, whilst working at Goldman Sachs, he broke the EU rules on lobbying by using his access card to EU buildings - which he was entitled to have as an ex-Head of the Commission - to simply enter into those buildings and waltz over to the offices of sitting EU officials to lobby for Goldman Sachs. The EU ended up revoking his access privileges, the first and only time that has happened for an ex-EU Commissioner.


  • Legally there are no Corrupt EU Commissioners. To be deemed Corrupt there would have to be actual evidence of Corruption (such as recordings of meetings were they explicitly promised to use their power in a certain way, in exchange for some form of payment, which normally only the Police has powers to obtain), them being subsequently charged and a Court Of Law convicting them for the crime of Corruption.

    None of them was ever just investigated for Corruption, much less convicted so pointing fingers at any one of the them explicitly and saying that they’re Corrupt would be Libel, which in my country (which by the way, is pretty Corrupt, with actual ex-government members convicted of Corruption) is an actual Crime prosecuted by the local Prosecution Office, not merely a civil lawsuit for damages.

    So if I was to name names, I would be putting my head of the block for the Crime of Libel. Obviously I’m not going to do that.

    What there is are various coincidences of EU Commissioners which acted in very positive ways towards certain industries and then after leaving the Commission went to work for those Industries making a lot of money, even thought they had no background in them (never before had worked in said Industries, no Educational training for said Industries).

    Since the police never investigates it, all there are are such coincidences of commissioners ending up in gold plated gigs in the industries they helped whilst they were commissioners.

    I’m not going to put my head of the nose for you by naming names (I’m not a Legal expert so don’t want to risk committing the Crime of Libel by doing so). I suggest you start by looking into were the EU commissioners during the 2008 Crash (during which the commission was very pro-Finance) ended up working afterwards.


  • That’s because Fascism is the natural end state of unfettered Capitalism as monopolies and cartels form naturally under it over time for most things and capital (which in Capitalism is Power) increasingly concentration, thus Corruption in Politics explodes which in turn accelerates monopoly and cartel formation and thus capital concentration in a vicious cycle.

    However homophobia is not an inherent problem of Capitalism, it’s an inherent problem of what Capitalism innevitably leads to if it’s not stopped.

    (All of this IMHO).



  • True.

    That is however a pretty hard and time consuming change, so to me it makes sense that in the meanwhile we take steps to reduce the harm caused by the system still in place, not least by cracking down hard on Corruption and Conflicts Of Interest and closing the legal loopholes that allow certain politicians to stay within the Law whilst purposefully using today the power they have been delegated to do favors for others who have promised them monetary payback for it tomorrow.

    If you’re drowning now you don’t put all your hopes on the ship that might be coming but isn’t even visible yet.



  • I believe the EU Parliament has to approve this so they can block it, and that’s elected by Proportional Vote and we all have MEPs there who, unlike national parliamentarians in countries without Proportional Vote (which are most of them) have to worry more about the public opinion in their nation turning against them.

    So if this shit ever makes its way to the EU Parliament (were the EU Commission will try to make it pass quietly), contact your country’s MEPs and show you’re well aware of it.


  • Whilst I do not agree with the spirit of the message of the previous poster, I must point out that specifically the EU Comission - from were this came - is not elected but nominated, and the nomination is one big horse trading shit show several levels removed from voters, were everybody but the head of it is chosen by the Council Of Ministers (which only represents EU National Governments , not National Parliaments) so the whole thing is maybe slightly more “democratic” than nominations for the Chinese Politburo.

    (If there is one thing that needs changing in the EU political structures, it’s the crooked, rotten shit show that’s the EU Commission).

    That said, the EU Parliament which can stop most of this shit, is elected and it’s even via Proportional Vote so there is no mathematical rigging at all to make some votes count more than others (unlike in First Past The Post Power Duopoly countries like the US or Britain) and hence voting in the EU Election does matter.



  • TL;DR

    QLC drives have fewer write-cycles than TLC and if their data is not refreshed periodically (which their controllers will automatically do when powered) the data in them gets corrupted faster.

    In other words, under heavy write usage they will last less time and at the other end when used for long term storage of data, they need to be powered much more frequently merelly to refresh the stored states (by reading and writting back the data).

    So moving to QLC in cloud application comes with mid and long terms costs in terms of power usage and, more importantly, drive end-of-life and replacement.

    Quad Level Cell SSD technology stores 4 bits per cell - hence 16 levels - whilst TLC (Triple Level Cell) stores 3 bits - hence 8 levels - so the voltage difference between levels is half as much, and so is the margin between levels.

    Everything deep down is analog, so the digital circuitry actually stores analog values on the cells at then reads them back and converts them to digital. When reading that analog value, the digital circuit has to decide to which digital value that analog value actual maps to, which it does by basically accepting any analog value within a certain range aroun the mathematically perfect value for that digital state.

    (A simple example: in a 3.3V data line, when the I/O pin of a microcontroller reads the voltage it will decide for example that anything below 1.2V is a digital LOW (i.e. a zero), anything above 2.1V is a HIGH (a one) and anything in between is an erroneous value - i.e. no signal or a corrupted signal - this by the way is why if you make the line between a sender and a receiver digital chip too long, many meters, or change the signals in them too fast, hundreds of MHz+, without any special techniques to preserve signal integrity, the receiver will mainly read garbage)

    So the more digital levels in a single cell the narrower the margin, the more likely that due to the natural decay over time of the stored signal or due cell damage from repeat writes, the analog value the digital circuitry reads from it be too far away from the stored digital level and be at best marked as erroneous or at worse be at a different level and thus yield a different digital value.

    All this to say that QLC has less endurance (i.e. after fewer writes the damage to the cells from use causes that what is read is not the same value as what was written) and it also has less retention (i.e. if the cell is not powered, the signal decay will more quickly cause stored values to end up at a different level than when written).

    Now, whilst for powered systems the retention problem is not much of an issue for cloud storage (when powered, the system automatically goes through each cell, reading its value and writting it back to refresh what’s stored there back to the mathematically perfect analog value) with just a slightly higher consumption over time for data that’s mainly read only (for flash memory, writting uses way more power than reading), the endurance problem is much worse for QLC because the cells will age twice as fast over TLC for data that is frequently written (wear-leveling exists to spreads this effect over all cells thus giving higher overall endurance, but wear-leveling is also in there for TLC so it does not improve the endurance of QLC).



  • Most people don’t actually know what they need until the see it, and the only ones who might are those who already have a process in place (hence know it in detail) and just want it or parts of it automated.

    People often do think they know what they want, but it’s a very general and fuzzy view, with little in the way of details and which seldom considers what should happen outside the most thread path of their process (i.e. things like error situations such as “what if somebody enters the wrong data in this form” or after the fact responsibility tracing in the form of usage logs and reports).

    It is actually a bit of an art to tease the details of the requirement from the stakeholders in a consistent and thorough way and also spot and get requirements for those “outside the main process path” elements and, frankly, in my career I’ve met very few people - even amongst business analysts - who are actually good at it.

    That said, what maybe the main advantage of Agile when done properly (with proper use cases and the actual end users trying the implementation of those requirements out) is exactly that it’s an interactive process to refine the requirements by cycling back and forth between requirements gathering, feature development and result evaluation to fill in missing details and tease out further requirements. IMHO, this is actually were Agile shines the most when compared to Waterfall, but as I said you need to do the requirements gathering and results evaluation parts of Agile (so the parts involving interacting with actual users bot upfront in making use cases and at the end of the cycle in evaluating the fitness for what they need of what was implemented) to get those gains, and most “Agile” teams out there seem to only do the fashionable parts of Agile like the “standup meeting” which aren’t what makes it most valuable as a process.


  • Well, seniority helps on the deadlines front: you can spot managers trying to force too short deadlines on you a mile away and throw it back at them (“I’m am the specialist, so I’m the one who knows best how long it will take”) and if they just try and impose deadlines you can bluntly state “that isn’t possible” and if they somehow have the authority to push them you make sure everybody (especially other managers, ideally the managers above them) knows that you’ve informed them upfront that such deadlines were impossible so when it inevitably fails, said manager can’t shove the blame your way.

    As for obtaining things from other teams, that’s a two part thing:

    • First make it painfully obvious in your estimates that a dependency on something from an outside teams exists. When inquired about progress, constantly point out that it will only happen “if that team provides us what we need to progress”. Keep reminding people that those deliverables are a conditional for yours - “they’re late our project is late”.
    • Second, start pushing them for delivering to you what you need well before you need it. It’s there, in your planning, so you know you need it and have some idea of when. The bigger the project the earlier you start pestering them. Persist on asking them for it, escalate to upper management if no movement is visible on their side. Make sure the groundwork is set so that if they’re late they get the blame on project deadlines being missed. It depends on the country culture but generally most people aren’t really impeccable professionals at time and priority management (and yeah, that includes managers) and tend to prioritize addressing “what’s burning harder” in their pile, hence why you need to start pestering them early, do it often and with more urgency the closer it gets to the point you need it (to make sure it’s perceive as an urgent need and rises to the top of their priority pile) and make sure the groundwork is set for them to be blame if your own deadline is missed because they were late and, more importantly, that THEY know they will get the blame (this generally at mid/upper manager level), so that from their point of view it’s “burning” (i.e. they’ll suffer if that doesn’t get picked up on time)

    Of course, all this requires competent management since they’re the ones supposed to do it and if your managers are trying to impose deadlines on you or using slimy trickery to get people to commit to shorter deadlines, they’re NOT competent managers - that kind of shit invariably yields death marches and bug-riddled results that in the mid and long term end up wasting far more time that it was shave by those shorter deadlines.

    Kinda sad that one has to play such games. Welcome to Mankind.



  • I think you’re confusing doing analysis before coding with doing all analysis before coding.

    If you do Agile properly (so including Use Cases with user prioritization and User feedback - so the whole system, not just doing the fashionable bits like stand up meetings and then claiming “we do Agile development”) you do analysis before development as part of evaluating how long it will take to implement the requirements contained in each Use Case. In fact this part of Agile actually pushes people to properly think through the problem - i.e. do the fucking analysis - before they start coding, just in bit-sized easy to endure blocks.

    Further, in determining which Use Cases depend on which Use Cases you’re doing a form of overall, system-level analysis.

    Also you definitelly need some level of overall upfront analysis no matter what: have a go at developing a mission critical high performance system on top of a gigantic dataset by taking a purist “we only look at uses cases individually and ignore the system-level overview” approach (thus, ignoring the general project technical needs that are derived from the size of the data, data integrity and performance requirements) and let me know how well it goes when half way down the project you figure out your system architecture of a single application instance with a database that can’t handle distributed transactions can’t actually deliver on those requirements.

    You can refactor code and low level design in a reasonable amount of time, but refactoring system level design is a whole different story.

    Of course, in my experience only a handful of shops out there do proper Agile for large projects: most just do the kiddie version - follow the herd by doing famous “agile practices” without actually understanding the process, how it all fits in it and which business and development environments is it appropriate to use in and which it is not.

    I could write a fucking treatise about people thinking they’re “doing Agile” whilst in fact they’re just doing a Theatre Of Agile were all they do is play at it by acting the most famous bits.


  • You can have airflow friendly design without the flat single color body, plastic interiors and a tablet on a plastic pedestal.

    Agreed that the whole SUV trend was a massive step back in so many ways, but being in Europe I’m not even comparing Tesla’s design with SUVs, I’m comparing it with other cars in the same category since they are still most of the cars in Europe.

    Even something like a Mini Cooper EV looks downright daring next to the stale styling of Tesla’s offering.

    The cars that I notice on the roads which leave me with the same overall impression in terms of looks as Teslas (minus the ugly tablet on a plastic pedestal look) are BYDs, which are way cheaper.


  • At this point in time Teslas stand out from the rest because they look like a mildly tweaked (mainly the higher back, inset door handles and big fat tablet in the middle of the dashboard) late 90s sedan or roadster design, because late 90s vehicles of these categories are the core visual styles they copied and tweaked in an attempt to make them look futuristic, a style which they haven’t changed since.

    (Maybe that stuff was very different from the common car in the roads in North America, but it wasn’t in Europe).

    The novelty value of inset door handles is gone, plastic interiors and big fat mid-dashboard tablets on a pedestal look ugly and dated, and the core car body design style just looks like your parent’s car back in the day.

    Tesla are kinda like those old Sci-Fi Movies from before flat screens and computer graphical user interfaces whose idea of futurism were fancier cathode tube screens and showing fast moving green screen text. The thing is, only beloved Sci-Fi filmic universes with cult followings (or alternative universe ones, like steampunk) still keep those visuals in any new movies, and Musk has been busy blowing up what little cult following Tesla had (which itself was already limited because, unlike Apple, Tesla never stood for quality and that following was mainly linked his own personal cult and perceptions of higher eco-friendliness than the rest, both now gone).