HNHacker News
TopNewBestAskShowJobs

7532yahoogmail

122 karma · joined June 7, 2019

submissionscomments
7532yahoogmail··on Automattic invests in Matrix
Off topic but the language here ... What is it about it that makes it plastic? For example it employs the phrases "that said" and "not least" which are generic, throw aways.

New projects are a kind of success itself so we expect the principals to be ebullient. But the prose is over the top. It gushes. Quantum computing wasn't invented here.

It's the IT corporate form of Hollywood but in words: Another theoretically innvoative industry except it isn't: It largely can't make an original film.

The older I get, the more I am in agreement with English Profs: use a better adjective, could you? Don't repeat. Avoid generic over used phrasing. In short: is it too much to ask that your language had a pulse? Game? Personality?

7532yahoogmail··on ‘Roe vs. Wade’ Plaintiff Was Paid to Switch Sides in Abortion Fight, Doc Reveals
Which is what the guy said.
7532yahoogmail··on MMU gang wars: the TLB drive-by shootdown
A hell of a good write up. I learned tons here.
7532yahoogmail··on Driving engineers to an arbitrary date is a value destroying mistake
Please elaborate on (3)
7532yahoogmail··on I invented Roomba and assure you, robots won’t take over the world
Oh c'mon ... Roomba is a PCA with a motor and basic sensors and what not. See comments above: nobody thinks Roomba confers distinction on the hardware or software side. So now what? We're gonna skip 10 magnitudes of 10 from simple to talking about "I Robot" material? No. It's used by millions of people for good old fashioned manufacturing reasons, and because it's cheap That's it
7532yahoogmail··on Driving engineers to an arbitrary date is a value destroying mistake
Consider a team of 8 who suck at estimation. Three questions:

1) is anybody aware the team sucks?

2) if yes are people open about it? If no, why not?

3) now what?

7532yahoogmail··on Driving engineers to an arbitrary date is a value destroying mistake
There's a lot to like in what you write. Back to the book I referenced above ... disagreeing here has several facets. First you have to be aware you can disagree. You have to be aware you have choice and use it. Disagreement is not a firing offense. Bosses are not entitled. Second, how it's done is important: if I disagree through a defensive behavior (again see book) that will go bad ... If at the end a decision is made and feel like I had no choice or my ego won't allow it ... well that's another potential concern. Again disagreement isn't often itself the real problem. The real problems are: what if I know I can disagree but I don't? Lack of courage my side or unsafe environment made by management? If management tells me they've made their decision contradicting my input which applies: I feel listened to and feel like my input was taken seriously? That's good. Or perhaps I'm insecure and can't deal with loosing control. If I don't have self awareness here I might blame, critisize management or play victim. That can be bad. Maybe I just can't admit my assessment was incomplete or wrong. Also likely to hit into problems. And in any of this I refuse to change, I can sink the team in the limit.
7532yahoogmail··on Driving engineers to an arbitrary date is a value destroying mistake
One of the big points in the book: at many human organizations trust/openness is the last thing resolved. And most people think openness is scary because it means being yelled at or leaving oneself open to be screwed somehow. There can't be openness unless there is safety ... Hence the ray dalio quote (and this comes many many variations by many people): working is doing dumb ass things you wouldn't be caught dead doing at one's own company. There's tons of ineffective labor -- people know better -- but won't say it because they are afraid about being screwed.
7532yahoogmail··on Driving engineers to an arbitrary date is a value destroying mistake
The issue often is that management will not crush programmers if wrong. Managers aren't stupid. This isn't a competence issue primarily. This is a trust and openness issue mainly. So the estimates were wrong? What do people believe about why they were wrong and how will people react? If that decends into defensive behavior ... Read the book.
7532yahoogmail··on Driving engineers to an arbitrary date is a value destroying mistake
Sorry, buy have to disagree. Management broadly (program or business managers and related workers) are not always wrong or wrong to ask. Nor is it waste to try. It's exactly this kind of fixed belief which drives behavior that ultimately runs the big risks. Not sure deeper meaning buy seeing this kind of interaction is a game, stupid game, or good idea by innocent if stupid people is exactly the kinds of things that work against team cohesiveness. Software isn't 6-sigma manufacturing so the best kind of predictive work that applies there doesn't work for us, but even they know good cross functional coordination is about a whole lot more than error bars. The book will give clarity and depth this forum won't permit. The inability to perfectly plan does not advocate for the "trust me model" from programmers.
7532yahoogmail··on Finnish basic income pilot improved wellbeing, study finds
The American system is or aims for equality of opportunity. Europe manages for equality of outcomes. These are vastly different. To make UBI work in the US is a much bigger uphill battle as a result. Now, it can be rightly argued that these remain goals to some extent. Civil rights weren't passed until the 60s in the US. So we can inveigh there where gaps remain. Finally, UBI cannot be seriously engaged and implemented without tackling tax breaks, and other social programs like Medicare/Medicade. Otherwise it's just more money. More money isn't always the answer
7532yahoogmail··on Driving engineers to an arbitrary date is a value destroying mistake
Software dev 20+ years: management is right to ask for estimates. It's ok for engineers to write a throwaway design paper to "get into" the problem before turning to jira epics and stories. It's also right for engineers to reject arbitrary dates, pressure to cut corners and so on. But this or the ops story absolutely don't get anybody anywhere.

You wanna move beyond anecdotes and nice sounding business arguments? Read FIRO by Dr. Schutz prob out of print or "Human element" by same. His son Ethan has updated these books.

Look, in normal high functioning groups conflict is normal. What confers distinction there is two things:

- no individual on team is ridgid and unchanging

- conflict is resolved with 100pct buy-in ie not cause the boss yelled, or you were out gamed, politics, favourites. IOW there is trust in the team (together with self awareness, competence etc which the book hits on)

When human factors burn down projects down the issues are quite a bit more about trust, individual self awareness, defensive behaviors, and not resolving the problem in a group way. Trying to eliminate conflict with rules of thumbs is a fool's errand. Conflict itself is not a sign of badness.

References to organizational modalities (the strong boss, the clear vision, and similar sounding approaches) help at the margins only and then only randomly.

7532yahoogmail··on Never attribute to stupidity what is adequately explained by opportunity cost
There's a lot to like in this article. I like how the author tries to remove manipulative motions (correspondingly paranoia) from the context in hopes people can see truer. Nontheless (I am 25+ years in software dev),

- some 20pct of people think the office is where politics and games are played. Thus they try to play it better. That's because openness at the office is usually quite low. Such people are unmoved by push back thinking themselves the smarter, grayer haired guy. Survivors of this kind of BS actually are smart, and do have experience with effective but distorting coping skills

- software should be a formal science. It's not almost all the time

- the chief issue unaddressed here but smartly lead up to is the management function: as the normal scenario is that resources are vastly drwafed by problems what do we say no to?

The management question when examined is complex and when it unfolds to systemic issues that are chiefly human not technical viz any of the corporate histories on quality improvement in the 80s/90s esp with company turnarounds. Ex. Detroit, Xerox, IBM under gerstner. While technical issues remain on the table, sustained under performance is ultimately rooted in management and company culture.

7532yahoogmail··on Re: Integrating "safe" languages into OpenBSD? (2017)
Gate keeping is a thing ... And I smell bad odors here and there from the bsd folks, but on the whole ... It's true: nobody is gonna trade across for equals on grep, ls, whatever. If rust wants to be some OS dev language it's going to have to make a better os or competive one (eg nextstep or k42 and similar efforts) ... It's going to have to go much bigger. And finally serious safe code would be accompanied by frama-c / tla+ proofs .. just pointing out rust is not the high ground.
7532yahoogmail··on Tell HN: C Experts Panel – Ask us anything about C
A ton of comments here talk about arrays and basic preconditions. See frama-c.com. even in c++ where encapsulation helps class/function contracts and unit testing is a must
7532yahoogmail··on Tell HN: C Experts Panel – Ask us anything about C
I agree which brought me into looking at Zig. A future version of C might disallow macros, preprocessor, disallow circular libraries, include a module system, but allow importing legacy libs like Zig. Also something like llvm so we can automatically do static analysis, transforms would be great.
7532yahoogmail··on Tell HN: C Experts Panel – Ask us anything about C
pascal_cuoq - Pascal Cuoq is the Chief Scientist at TrustInSoft and co-inventor of the Frama-C technology

This looks to be a hell'va' good tool chain. I'm playing with as of yesterday.

7532yahoogmail··on Ask HN: Programs that wasted you 100 hours?
Agree with both sides of latex
7532yahoogmail··on Ask HN: Programs that wasted you 100 hours?
Fixing plsql errors in Oracle. Only a c++ compiler in a bad mood gives more errors or as inscrutable ones ...
7532yahoogmail··on StarCharter – CLI tool for producing vector-graphics charts of the night sky
Dude: not only great idea, well executed: practical, direct, to the point
7532yahoogmail··on How do you know if you’re living through the death of an empire?
Trump referred herein as a bullshit artist is certainly a problem in his own. However, the OP is right arguing he's but a convenient and simple example of the subtler, slower moving problems. Of the three Federal branches, Congress confers distinction as that branch with the smallest reputation of institutional credibility. On any of the largest issues,

- campaign finance reform

- self dealing

- gun control

- taxation policies

- fiscal control

- immigration policy

- increasing deferral to the Executive branch on war powers

- health care cost inflation

- partial rollback of Glass-Stiegel act

- outsized influence of lobbyists

the underlying theme is willful and actual helplessness.

The dominant political parties increasingly represented corporations and the upper one percent whether it was the Hollywood A-class or gecko like corporations for profit. Why? Corporations have lobby money and it's easier to interact with fewer corporate contacts that tens of millions of dispersed Americans who lack a single contact point -- even though a House or Senate member has precisely that job.

Trump/Bannon saw their opportunity and took it.

Congress has no agency in the here and now. Politicians have succumbed to the outsized problem space increased by inaction in what has become an all too familiar trajectory:

- they try to position themselves as DC outsiders aligned with hardworking Americans and kitchen table issues whether by portraying us as spinless over anxious, over worked victims or heroic proletariat suckers who still manage the good fight

- They talk about what they will do in the always perpetual future

Once the campaign is over the realities of institutional incompetence cast a shadow so large it crushes pragmatic action.

And thus we become more disalusioned with Congress. In frustration and anger a sufficient number of people went Trump.

To use and abuse the Plato analogy, too much cheap symbolism of emotional issues has dominated our conversation about the shadows on the cave wall. We need but turn around and walk the 10 feet out of the cave entrance and do the practical things like clearing up our home camp. Yes, smart doing requires smart thinking -- the two are permanently entangled in the other -- so ideas matter. Dispositioning the shadows matters. But the Federal US government was never intended to be bully pulpit for the Christian right or inveigh on it. That's a problem for a father, mother, son, and daughter. The US government is about a human justice; it's about fighting structural and monied power that violate individual liberty.

Right now our cherished ideals are like the crushed and broken stained glass shards on the ground. So be it. Let's start the work of reassembling them an make anew meaning.

7532yahoogmail··on The Subtle Power of Booleans: Programming with truth and statefulness
Now, here's a great read. Loved it. I've used tla+ ... I'll give alloy a try too. I'm interested in anything else along these lines.
7532yahoogmail··on Ask HN: If I've already taught myself to code, should I still get my CS degree?
Yes you should. I learned development on my own and, yes, I landed lots of jobs. However there are barriers:

- without a cs degree several avenues of kernel development

- ditto distributed systems

- anything with a strong quantitative basis

- formal tools/tooling

- specialty data structures and algorithms

Will be beyond reach. You simply won't be able to cope. I went on to get a mathematics degree and that saved my bacon when older and had needs beyond a paying gig (read family and house).

Do not under estimate the need to write clearly. On above topics bubbles and arrows don't cut it. You need to write papers, and/or formally model if you want to communicate and prove non trivial results.

Learning languages is one thing. Having a deep understanding of the libraries that come with the language (simple example: STL) is also quite important.

Finally given a choice between a guy with a degree and a guy without ... The guy with shows he/she can finish something of difficulty in four years. This is not to say MIT grads are always better. But a degree is better than none.

7532yahoogmail··on Do not log
Some of the comments here are too wrong in the other direction. I'll come back to that. What I would have liked to see from the begining was something like:

If you must log then pipe the output into <????> which will store your log into a search system such that if you have a coordination id will bring logs from the various microservices together.

So what is ????

Log rotation, compression, disk space, getting FS space and making directories on large corporate networks is a pain. I also have to ssh around and compose logs. We also deal with servers in multiple timezones and most programmers are too dumb to put the TZ. Figuring out what TZ was ultimately used and sequencing it is stupid work. Yuck.

At my office the gdpr of logging is not well adopted. Logs are left in code really for debugging, to monitor a PR change in prod then forgotten later. You can see where that goes: waste

Also for a serious system with wide customer usage, the log should contain a errno like error (defined universe of errors with a set format), the use case, plus the details. Not whatever sprintf the programmer dreamed up.

The OP is also right here: logging is used as a bailout just in case thing because the programmer did not make a narrow contract in the method, service. Logging is used to find edge cases. That's not right.

Finally logs can be slow and some esp. c++ streams stuff may use mutexes.

7532yahoogmail··on On “The Battle Between the Frogs and the Mice”
Thank you. Enjoyed immensely
7532yahoogmail··on Memory-Efficient Search Trees for Database Management Systems [pdf]
Off topic to OPs paper however consider the case of volt-db an all in memory SQL db with replication. In the sales'y' write speed was written down to less locks, latches, disk I/O. But somewhere else I read that a big culprit in fact isn't that: it's formatting data to be written to disk then decomposing a disk block back into memory for use. All memory dbs avoid that. Thoughts ?
7532yahoogmail··on Memory-Efficient Search Trees for Database Management Systems [pdf]
Working my way through paper. Looks very cool. And practical ... It's also exceptionally well written. It's clear. Nice job
7532yahoogmail··on The automotive industry’s value-destroying addiction to capital (2015) [pdf]
Your rant + some good points to be sure reminds me of a long running argument I had with an ex-detroit guy on who the mororns and/or cheaters were: Detroit or Japan? -- this was mid 80s and early 90s. Hint: some American companies are slow to learn. That was my argument then.
7532yahoogmail··on The automotive industry’s value-destroying addiction to capital (2015) [pdf]
How does the Japanese of the 80s and early 90s (before their problems recently) differ from now? JP took some 30pct of the US market in an industry that is/was largely beholden to the same constraints you mention. Honda and Toyota we're good investments then.
7532yahoogmail··on The automotive industry’s value-destroying addiction to capital (2015) [pdf]
One thing I question is the assessment that what's under the hood is unimportant to the customer ... Now many guys and most wives surely don't care unlike a mechanical engineer until it doesn't work. In the early 90s Japanese cars cost more but consumers saw quality. JP took 30% of the US market as a result. Wouldn't this be better examined in terms of how repair costs factor into customer assessment of car desirability?
← PreviousPage 2 of 4Next →