HNHacker News
TopNewBestAskShowJobs

HereBeBeasties

316 karma · joined March 30, 2016

submissionscomments
HereBeBeasties··on Ask HN: Are books worth it?
> I hate wasting time, so last year I gave audio books a try

Interesting. I have exactly the opposite reaction to audio books. I hate wasting time, and audio books don't let you skim sections that aren't of much interest (essential if you want to read a lot of non-fiction IMO), and generally take massively longer. I can read a good deal quicker than people talk. I dunno, maybe 5x speed or something?

Treating reading the printed word as a waste of time is madness.

HereBeBeasties··on Flutter vs. Other Mobile Development Frameworks: A UI and Performance Experiment
I had some similar initial issues getting it working (also suffered from the comedy issues with not being able to run Android Studio on modern JDK/JRE versions due to JavaFX stuff being removed).

After I'd faffed about and made it all work I must say that Flutter itself felt very nice. The hot-reload alone is enough to make you massively more productive. Dart is a perfectly reasonable language too, much nicer and better thought out than JavaScript, even with Typescript on top. Integers that are, for a start...

HereBeBeasties··on Cerebras’s giant chip will smash deep learning’s speed barrier
Yes, that's what their web site says.
HereBeBeasties··on Hard deadlines are not user-first
We tend to try to do any vaguely longer term/important estimation as a team exercise, which ends up with people talking each other's estimates up, not down - you explore the problem space more effectively as a team and a lot of "but what about X" stuff comes out of the woodwork then.

If you have a manager who sets your team up for pressure and failure by artificially revising your estimates down, without cutting the scope of the work, then personally, I would find a new manager. Source: Am a manager.

HereBeBeasties··on Hard deadlines are not user-first
IME, if the manager is primarily coming up with the estimates, rather than the team, you're doing it wrong. (And are doomed to an eternal cycle of blame, stress and lack of trust.)
HereBeBeasties··on Hard deadlines are not user-first
Define "trust". As an industry I think we often talk about the wrong things here. People look at this from the point of view of controlling IT & developers (controlling costs, deadlines, functionality, etc.) when really everyone should be looking at it instead from the point of view of maximising value to the business. That's what Agile is really all about - it should really be about trusting that people will make good decisions based on the currently available info (which will likely be different than when you started the project), do good experiments, and find good compromises. This is especially true if unforeseen delays to a team's work has a knock-on effect on other people (which a good manager will try hard to decouple and avoid, deliver incrementally to lower the risk, or at least include healthy contingency for).

IMO, you should only really care about imposing deadlines as an answer to the question "how much time is it worth investing in solving this problem?" If the scope of the solution becomes larger than expected, and it starts to look like it won't pay off, abandon it and start doing something else instead. You had a good experiment which was entered into in good faith based on the data available at the time. That's the nature of experiments. Learn your lessons and try the next one.

Trusting that your teams have good plans that fail early and incorporate fast feedback loops is generally the only real way to make sure that they have realistic scheduling/deadlines for those plans and that they are likely to generate real value. It amazes me how many people in management seem to put their efforts and emphasis mostly on scheduling the plans, rather than the plans themselves. I guess it's easier to come up with estimates for things, than it is to come up with good strategy and business value propositions/justification.

I really recommend reading "A Seat at the Table" by Mark Schwartz (ISBN 9781942788119) for a good exploration of how agile meets management trust issues, budgeting and longer term planning, and how to try to break down the barriers between "IT" and "the business" (when in most modern companies, IT is the business).

HereBeBeasties··on Challenging projects every programmer should try
I think the original commenter knows full well what an array is.

Vague justifications like "can cause problems" is probably exactly what he's referring to, in fact - people who know that inserting elements into an array is "slow" and end up making large and complex code as a result. Yes, it's O(N) on the length of your code, but the point is that for a couple of megs of text, O(N) is perfectly acceptable.

At least on a desktop, that'll fit in L3 cache which these days is around 175GB/sec. Or to put it another way, inserting that single char can probably be done at around 40,000 times per second. Which is faster than I can type, at any rate.

HereBeBeasties··on Ask HN: Where to start with enterprise-level security and procedures?
I think that site pretty much nails it, especially SSO (depending on what you're doing you probably want LDAP, SAML and OIDC/OAuth2) and audit logs.

It misses a couple of other nice to have differentiators, though:

The ability to pay by invoice to their purchasing department (you probably want to insist people do this upfront and yearly and not monthly, to avoid the pain of chasing people). Plenty of enterprises won't be able to buy your product without this.

Some decent consideration given to self-service (which RBAC might cover, but best to be explicit), by which I mean that you can delegate admin control such that you don't need to put in tickets with the team that runs the system in order to get changes made to its configuration. (Example: GitHub enterprise let's you set up multiple orgs, so you can give each dept. or team an org to do what they like with.)

If you put some thought into granular permissions from the beginning (in the GitHub case, for example giving away perms to create repos, but not allowing that user to change how auth works for the org, for example) you will avoid pain later.

APIs. Dependent on product, but ideally design your UI so that it is backed by an API that lets me do everything programmatically, so I can drive your product with other integrations via we hooks, or GitOps, or whatever else I want to do.

HereBeBeasties··on React in concurrent mode: 2000 state-connected comps re-rendered at 60FPS
Flutter looks like it could be quite interesting for this - on mobile it compiles over to native machine code and uses GL or whatever.

I haven't looked at the details for web, but I think it does webasm and canvas, etc. and with the architecture they have it could potentially be a lot faster than traditional JS frameworks https://flutter.dev/web

HereBeBeasties··on React in concurrent mode: 2000 state-connected comps re-rendered at 60FPS
It's also used quite extensively for data visualisation roles that D3 has traditionally been king of, in fact often alongside D3's libraries for calculating axis tick marks, colour scales, etc. To that end, you actually do end up with thousands of DOM nodes quite often.
HereBeBeasties··on Google AdWords charged me for clicks in Istanbul while location-targeting the US
Define "sustainable".

Seems like it encourages companies to get in a bidding war against each other in a race to zero profit margins, while Google pockets what could have been their revenue.

HereBeBeasties··on Tesla PowerWall 2 Hack
Their customers do, though, and that's the whole point. Without giving people a short, reasonable time to patch, you're part of the problem, not part of the solution. For what it's worth, you are also coming across as something of a zealot, rather than a reasonable person who sees the world in shades of grey.
HereBeBeasties··on Patterns for Writing Simple Code
The irony! A post on writing simple code having as its first suggestion the use of abstract factories. Am I on /r/nottheonion?
HereBeBeasties··on Dependency injection is dynamic scoping in disguise
> The reason why we have DI and DI frameworks is because we are asked in requirements to make things configurable out-of-code (and at runtime)

That's a reason, but it's far from the only one. The way I've seen DI used over the years is far more about separating out concerns in the code via interfaces, or making things testable without side effects, than it is making those things dynamically pluggable / controllable via config, not code. The majority of interfaces passed as dependencies into constructors have a single real implementation (outside of unit tests).

I lately err on the side of explicit manual wiring as the cost saving of doing it all automatically does not usually offset the costs of extra magic and lack of compile-time safety that it incurs. Exceptions are where there is a lot of AoP interceptor stuff to wire in, or if I want something to help with lifecycle scoping (e.g. per-request lifetime for a set of related things), at which point a DI framework will likely start paying for itself.

HereBeBeasties··on Dependency injection is dynamic scoping in disguise
Please do. IMO, this was very well written, well-paced and interesting.
HereBeBeasties··on Evaluating Bazel for building Firefox
I have to ask, "so what?"

Provided the abstraction doesn't leak I really don't care, in the same way that end users of Microsoft Word don't care about the algorithms that kern their text, about how DirectWrite does subpixel rendering, or anything else.

Yes, it's all fiercely large and complex. The original user is pointing out that this is all hidden for simple projects, waiting in the wings for when you need it, and therefore doesn't matter.

HereBeBeasties··on Google T5 scores 88.9 on SuperGLUE Benchmark, approaching human baseline
If you teach others English, please learn the difference between "none" and "non". You mean "non-standard" in all your examples here (if British) or perhaps "nonstandard" (if American).
HereBeBeasties··on If You Run a Small Business, Park in the Back of the Parking Lot
I have recently become a customer of Bulb for my energy. They won me because when I tried to sign up and this failed, they followed up with an email explaining that my existing supplier had a weird set up for my smart meter which made it impossible to take over automatically and how to get them to fix it, which appeared to have been written by a real human.

In most companies, that'd just be an error in a log file somewhere. They then followed up later to ask if things had been handled well. They also have one single, good value tariff with no option not to have green energy.

Principled, with A++ customer service and a competent mobile app, complete with a time line for switching and starting my account with them. I'm totally sold. They could be quite a lot more expensive than my existing supplier and I frankly wouldn't care given the whole experience so far.

HereBeBeasties··on Web-dev nirvana, and why I needed to let go of React to reach it
> You can’t just create a React app.

Only you can. React on a CDN works and create-react-app is but a one line CLI invocation to... create a React app.

> we’d need to get rid of Webpack, since it’s difficult to comprehend and customize

Is it? You don't really need to customise create-react-app and even if you did, Webpack has good docs.

> We’d drop Babel too, since transpiling creates a workflow burden (especially for debugging).

Bit slow to start up the dev server, I grant you, but we're talking seconds here and how often do you do it? Hot reloading is instant. Source maps work. This feels fairly false. Importantly, the tool chain will check my code for issues, making my work flow much better. Especially if we throw in typescript. It also lets me use things like lambdas, again making me more productive, not less.

> we can end up with a codebase that’s shockingly React-like, without the workflow and maintenance overhead

Except for maintaining your own custom router, event handling, wrapper around some popular CSS framework so that you don't have to style everything explicitly, and all the rest of it, of course.

> It’s hard to overstate how much easier it is to develop once all the extra tooling and abstractions are gone.

It's hard, because it isn't really easier, is it? What specifically is easier? Having to make and debug all your own custom everything, including your own leaky abstraction? Having to figure out how to optimise the site's performance because you've thrown away the virtual DOM and all the benefits that brings? Having to write your tests against a real browser's DOM engine?

> You save a file, you refresh the page, and you see your changes.

That works just fine with create-react-app, etc.

> You can read your stack traces.

I already can, thank you.

> You can pause execution and not be lost.

Have you heard of breakpoints, or run to cursor? I'm not sure what this even means - does the author mean hitting the pause button in the debugger randomly while rendering the page?

> You can spend all of your time working on your app, instead of chasing down obscure build issues.

I already do, thank you. I suspect chasing down obscure build issues is comfortably less than 1% of the problem. I suspect it will be more than that if I follow the author's advice by "creating a production-only build", which will make my prod and dev environments wildly diverge. No thank you. I already have a production-ready build backed by battle-tested tools maintained by someone else.

This looks strongly like a toy solution in search of a problem.

No one would advocate building your own custom C++ compiler just because you don't use all the features of the language. This is basically the same.

HereBeBeasties··on Web-dev nirvana, and why I needed to let go of React to reach it
The hidden benefit is that when your small project becomes medium sized, you won't need to rewrite it all from scratch...
HereBeBeasties··on Stop Infinite Scrolling
I do this on one of our internal sites at work - it makes a table that is fitted to the page vertically, where scrolling with the wheel changes the page. Super easy to flick through results (better than infinite scroll in fact), which is the main issue I have with paginated things.
HereBeBeasties··on Should small Rust structs be passed by-copy or by-borrow?
Although your point is sort-of true, but I don't really see how it's valid here. The author is talking about the performance implications of the two approaches in situations where the function parameters are not mutated. Suggesting that user "makes the choice" here by taking defensive copies for themselves will probably (but who knows what the optimisers will do - they might just elide it) make performance worse. It's not something end users will think to do, anyway, at least not in the name of performance.

Regardless, I want a library author to help me fall into the pit of performance success, not expect me to do it all for myself.

HereBeBeasties··on Software architects should be involved in earliest system engineering activities
Nearly all the software you actually use. Do you think things like Vault, Consul, Kubernetes, Apache, Nginx, NodeJS, NPM, React, VueJS, etc. etc. etc. were all "mature" one year in? Many of those are actually extremely simple and limited in functionality compared to actual "real" enterprise apps. What an amazingly naïve comment.
HereBeBeasties··on All the best engineering advice I stole from non-technical people
Clearly NASA's Apollo programme would have been more of a success with only one or two people executing it. Or the Large Hadron Collider. Or the Linux Kernel (and no, that's very much not the work of one person). Or anything else of any real scale or import.
HereBeBeasties··on Dark emerges with ‘deployless’ software model
I made a mistake mentioning Prometheus - it's the least important point in my post. I get that you may provide something for monitoring (performance and tracing, at least) that's more baked into the whole AST/graph model and that sounds really very compelling. And obviously end developers won't need to monitor the systems/services because as far as they're concerned there aren't any. It feels a bit like electric cars - a bunch of new (and hard) problems arise, but it's compelling as a bunch of older (also hard) problems just cease to be. Huzzah. I'll certainly agree with you that the potential upsides here are very large and very compelling.

But the need for things like code review tooling, test coverage reporting and mocking frameworks (yes, I will want to isolate stuff via mocks) aren't going to just disappear with this kind of model. They're far from exotic use cases for the kind of business customers you will need to scale this and get real adoption and thus positive cashflow, more of a necessity. It's a real leap of faith to think it's worth rebuilding so much of these kinds of ecosystems that have taken thousands of man years to evolve and develop for existing languages. And if you don't have plans to provide that sort of thing you'll be missing out on most of the market, I would have thought. Yes, you'll get hobbyists but surely they won't provide the volume or reliable subscription-style revenue you'll surely need to make this sustainable?

Unless of course your endgoal here is being bought out by Google, in which case fair play. This is cutting edge thinking and tech, full of nice hard problems to work on and lovely "oh but if we just don't have that then we don't need this either, or can do this like that instead" type insights to be made. Cool stuff, but it still won't get me to bet the farm on it. I really do wish you well though!

HereBeBeasties··on Dark emerges with ‘deployless’ software model
Your vision is extremely compelling and well articulated.

I'm not sure I buy the "coalescing multiple things into one makes things simpler" argument - the simplicity comes at the expense of expressiveness, flexibility and optionality. A large, highly-opinionated monolith, right the way across the stack, is bound to have made some design trade-offs and decisions that are either plain wrong (we all make mistakes) or don't fit with however I want to actually use it.

To do this at the AST graph/language level strikes me as both genius and absurd - not only is language design very hard, but you clearly have a massive uphill struggle to provide sufficient library and framework-level code on top of that to be able to start to compete with more mature options. Not to mention things like code review tooling (it's neither text-based, nor even in any form of conventional revision control system, so likely start from scratch). Security controls, auditability, vulnerability management for any library ecosystem that springs up around this, etc. etc.

By rejecting text you are having to reinvent and support a compiler, an IDE, github/gitlab (or equivalent, with their massive functionality set including protected branches and security controls and the like), package management maybe, debugger tooling (on the web), release/rollback systems/UIs, perhaps even monitoring and alerting (because you're promising the users they don't need to run infrastructure/services like Prometheus and the like and your "roll out" process looks so different).

Does Dark really have sufficient expertise around all of that to want to make this stuff totally monolithic? Is it even possible for a startup company to really compete in that sort of global (massively open source) scene?

Convincing people to bet their company on your company, both as an ongoing enterprise and as a place that can get all the inherent trade-offs here well-matched to their individual use-cases is going to be an almost impossible sell. Regardless of how much you assert that you believe in your mission and don't want to ever pivot. You can't blame people for being sceptical, especially when the opening paragraphs essentially say "this is a silver bullet".

I wish you luck.

HereBeBeasties··on Tesla Q2 2019 Letter
They've achieved a 0.5% increase in production volume in Q2, compared to Q4 2018, to 87,084 vehicles. I'd hardly call that "rapid progress". For comparison, Toyota make around 2.2 million vehicles per quarter.

A more reasonable brand comparison might be Mercedes-Benz Cars, which made 575,639 vehicles in Q2. It's quite impressive that Tesla have got to about 15% the volume that Merc do, but they're hardly going to take over the world with that kind of growth rate.

IMO they should stop chasing volume sales of lower cost vehicles and concentrate on premium vehicles with higher margins. What's the point of killing themselves trying to lift production numbers to try to make all the analysts who seem to be obsessed with that happy, which doesn't yet seem to be working, if the margins aren't worth bothering? It won't end well.

HereBeBeasties··on Authentication and the Have I Been Pwned API
Doesn't take much imagination to find a use.

Assume I find Anna's email address as part of a breach somewhere.

Hello Anna,

We value transparency and honesty highly at $p0wn3d_company. To that end, we're sorry to have to tell you that our systems were compromised by an unknown hacker recently. Although we believe that no personal data has been stolen, we are working with Government agencies and expert security consultants to determine the full extent of the breach.

As a precaution we are asking our customers to change their passwords, which you can do by clicking on >this link here to a website that looks like ours but is actually owned by a hacker<.

Etc.

HereBeBeasties··on Show HN: BaseTable – a Table component with high performance and flexibility
Don't be so rude and mean. Someone's poured tons of time into this and given it to you for free. It also looks really good, if you'd get out of your own way and actually bother looking at it. Where's your huge, popular open source project with amazing doc site?
HereBeBeasties··on Breaking max efficiency of solar cells by activating 2 electrons with 1 photon
There's nothing wrong with solar per-se, but it's just not sufficiently power dense if you're talking national scale power usage. https://www.finder.com/uk/solar-power-potential seems to think that countries like the UK would need more than 10% of their area covering with solar panels to cover their energy needs. I think you'd need to be talking about an order of magnitude improvement in efficiency to really start making it look really feasible as a significant way to change our fossil fuel usage, no?
← PreviousPage 4 of 6Next →