HNHacker News
TopNewBestAskShowJobs

mr_tristan

1,282 karma · joined October 3, 2015

Greybeard engineer
submissionscomments
mr_tristan··on Your Language Sucks, It Doesn’t Matter
If Kotlin can set up adequate tooling and performance in native and JavaScript backends, its approach of building libraries for multiple platforms could be a new wrinkle, and fulfill the "write once, run anywhere" better than Java ever did.

As it stands, it's _not_ easy to use the multiple platform setup. You really need to be both an expert in Kotlin, Gradle (and their plugins are _barely_ documented), and the target platform.

But if the build process becomes easy, and, they can build a rich ecosystem that basically can create abstraction layers on top of the target platforms, I see it going far. It's still not there yet, but it's moving quickly.

I'm still in a "wait and see" place with Kotlin. I've enjoyed working with it on the JVM, where the tooling is fantastic. But the JS and native toolchains are still not up to my standards. Just being another JVM language isn't good enough for me.

mr_tristan··on Why a Slack Backlash Is Inevitable
A favorite quote: "culture eats strategy for breakfast".

Slack and Teams just feed this instinct to spew thoughts without thinking about your communication first. Everything about modern society reinforces this. And it's not remotely generational; or, I haven't noticed much of a difference between generations in regards to depth of conversation. It's just different tools of choice.

So, I'm sure everyone will hate these tools, but really, they just haven't figured out how to communicate deeply and meaningfully together. And no tool is gonna make that happen for you. It's a culture problem.

I'm 100% sure if they ban Slack and Teams, and go back to email, everyone is just gonna hack email to say all the same stupid crap they're saying right now. Maybe it'll slow things down a bit, but I can't see it transforming much of anything.

mr_tristan··on Spotify CEO: musicians can no longer release music only “once every 3-4 years”
Since independent venues have been gradually disappearing in the US in the 21st century, and ticketing is locked down by Live Nation, it sure seems that the only revenue stream American musicians can control is their merchandise.

Makes sense that everything else is just "marketing" these days.

I'm sure this has an impact on who decides to make music professionally. Why stick with it, only to sell your own t-shirts? (Note: I can't figure out how to get trend data for from the Bureau of Labor and Statistics, to see if that question has merit.)

mr_tristan··on All of us test in production all the time (2019)
I've found the problem isn't being on call, it's being on call PLUS not having control over priorities.

When doing it right, owning the on call experience can be a valuable learning experience. But this usually means having extra time to do things like develop integration and performance testing environments. And access to make whatever changes needed to happen, happen.

But a lot of places are like "nah, you're being a perfectionist". And then expect you to magically respond to issues with vague descriptions and no diagnostics. And yeah, that sucks.

mr_tristan··on A $500M call option on home gyms
I just remember: at the same time the fitness industry has grown in the United States, there is also an obesity epidemic. And I really don't think the people who are really into fitness are the ones spending the majority of the money. It really seems like it's the less intense, "average joe" folk where the green is at.

I recall how a lot of "globo gyms" make tons of money at $10-40 per month, and why a boutique gym struggles at $200 - the globo gym capitalizes on people basically buying a membership, and basically not sticking with it, but... you know, not quitting just out of guilt.

And it sure seems like Peloton established that the $39/month price point can work.

If the Coronavirus problems extend into 2021 (very likely), I bet this purchase is going to be real amazing, since there will be a grip of Average Joes who will probably fork up the big purchase for Christmas to start up classes as a New Year's resolution, and then just stick with monthly classes "just because"

mr_tristan··on The Rise of Platform Engineering
My mind went immediately to a Netflix presentation about "the role of central teams in devops" a couple of years ago: https://www.youtube.com/watch?v=xA1qPQg3WTc

The big thing I remember about their approach that surprised everyone: there was no mandate to use the platform/central team's tools. It made me chuckle how many times the presenter was grilled by everyone about that. It was like some of the audience straight up thought he was lying about that.

But basically, if you have a platform team, and a mandate to use that team's tools, well, the other teams aren't really "customers", in the sense you can leverage choice as a signal. So you have to make up for that. In my experience, you need very good management, and constant, multifaceted communication. Which... might work, might not.

It's probably best to delay any kind of centralized/platform work until you have a _very_ clear pain that defines a very clear set of roles and requirements. Unless everyone says "Oh shit this is amazing" ... just say no.

mr_tristan··on Create diagrams with code using Graphviz
I’d actually start with Tufte: https://www.edwardtufte.com/tufte/books_vdqi

There are standards like UML, but I’ve never found those to be as useful to start with. It’s best to treat this as a “design problem”: first, answer the question: “what am I communicating”.

Then, maybe look into conventions - but often you’ll find less need for one “master UML diagram” and instead use many, smaller diagrams embedded within reference docs.

I feel like project reactor did a good job here: https://projectreactor.io/docs/core/release/api/reactor/core...

Personally I’d like to see more related to inheritance, but I’ll take what I can get. The tooling can be a pain to embed automatic diagrams in

mr_tristan··on Blogging Is Not Dead
Unfortunately, blogs == spam in a lot of the non-technical world.

The /r/woodworking subreddit used to have a strict "no blogs" rule that finally got relaxed to just be more "no blog spam".

I noticed similar problems in Pinterest, where you'll find pins that have beautiful images but lead to spam garbage. So, there might have been a page that was initially hosting the image (probably copied from somewhere else), but then, it gets swapped out with an advertising garbage site. And the pin goes up in popularity because most users just don't care about the backing site.

The wider the potential audience, the bigger the potential for spam. And it sure doesn't seem like there's a great, consistent way to filter spam. Search engines do not appear to have kept pace since the rise of walled garden social networks.

At this point, I would pay for curated, interesting updates. It's just hard to see how a product like that would easy to find these days.

mr_tristan··on Language Design: Use 'ident: Type' not 'Type ident'
In Kotlin, IntelliJ has no problem with this. As you type a new value: `val id`, and you have `IdentName` defined in scope, the value `identName` is suggested automatically.

Not all IDEs are the same, though, and I'm not sure how sophisticated this feature was to implement.

mr_tristan··on Remote Work Report
> 43% of remote workers feel it is important to work for a company where ALL employees are remote…

As a full time remote worker, I've also felt that having everyone else is great. In every case I've work with a colocated team, they end up snubbing you in weird ways.

This snubbing is just a cultural thing. There's no technical reason remote workers should feel left out if working with another team.

I've found that most colocated team members rarely write well, and often do not track, or even follow up on complex team decisions. When everyone is remote, it often forces some better communication. Frequently, the teams have to "double up" on the media used to communicate, which almost always requires some written communication.

Now that everyone's remote in quarantine, I've heard complaints from the colocators about "having to overcommunicate". But really, it's just learning to communicate well.

This metric of "how many all-remote workers want everyone else to be remote", really seems like a great test for "how well does your company communicate?"

mr_tristan··on Configs suck? Try a real programming language
This is a good example of a structured approach, with the caveat that there are multiple phases.

With gradle, there's three big phases: initialization, configuration, then execution. (See https://docs.gradle.org/current/userguide/build_lifecycle.ht...). I'd think you'd need to do something similar with any structured configuration DSL - have distinct phases where you may "init, plan, apply", etc.

This, it's a pretty complex problem to have. But that complexity may be worth it as part of a "developer productivity engineering" effort, where you're really looking to use data to minimize the time between a configuration change, and the time it's applied in a runtime environment. Doing that is a hard problem.

mr_tristan··on New iPad Pro with LiDAR Scanner and trackpad support
For 3D modeling, I've still not found a replacement for Fusion 360. It does appear that there are products like shapr3d that are interesting for some basic conceptualization, but, there aren't things like, say, a sheet of default variables you can use to restrict your design to. It seems like these tools are for some rough sketching, but, the intent is probably to move the concepts into a desktop CAD system.

This makes me wonder how big the iPad software market really is in comparison. It seems "tethered" to other platforms.

mr_tristan··on New iPad Pro with LiDAR Scanner and trackpad support
For music production, I lost my best audio inputs, like the Apogee One, when "upgrading" to the iPad Pro. This was purely a move on Apple's part, and it appears that Apogee is not just going to do much about it: https://knowledgebase.apogeedigital.com/duet-ipad-mac/apogee...

It's significant because Apogee was a _partner_ and this device shows up on the _Apple store under music creativity_: https://www.apple.com/shop/ipad/ipad-accessories/creativity?...

Keep in mind this $300 device is a brick on the new iPads.

At this point, I'm loathe to purchase anything just to work with the iPad Pro, because these devices work fine and continue to work fine with my other devices.

This appears to work for _electronic_ music just fine, however, but for demos the iPad is a fantastic platform. But now you're left with... figuring it out, I guess.

mr_tristan··on New iPad Pro with LiDAR Scanner and trackpad support
What is the size of the app market for iPad software? Does this device matter to that market?

I still feel like my own iPad usage is mostly locked by a weak software ecosystem, and while the hardware is impressive, it still seems like complete overkill for the current ecosystem.

I want to use it more, but the software for things I would have expected on the iPad, like 3D design, music production, etc, are often limited, either by software or connectivity issues.

I've gotten more use out of my Linux notebook running a Windows VM. Which surprised me.

I just get the feeling that the only people really making serious money on iPad apps are games, which are probably just ports of phone apps.

mr_tristan··on I Don't Use Classes
I've noticed that in large Java hierarchies, where I spend a lot of my time, people often use interfaces where they really should be using modules. Like, there's this vague concept of a "service" and methods of this service are bound together via an interface. Which ends up coupling all kinds of weird dependencies in the class definition.

My guess is that this is a similar case in Typescript that the author is describing.

So, this approach is, instead of having IFooService with two methods, IFooService.doOneThing and IFooService.doAnotherThing you just have a package "fooservice" with functional interfaces DoOneThing and DoAnotherThing. This seems to still play nice with most of the tooling, and often, keeps the code simpler and makes it easier to refactor. DoOneThingImpl and DoAnotherThingImpl can easily share code, but that aspect shouldn't matter at all to the caller.

Another way of thinking about it: don't worry too much about a perfect interface for layering your business logic initially. Start with just some functions, then as you spot patterns you may recognize there's a state pattern that does things better. I don't think this is really specific to Typescript.

mr_tristan··on Ask HN: How are you preparing yourself for a recession?
I was just going to say "I'm just getting off my ass and tightening up my financial habits".

For those of you like me, who like spreadsheets but don't know exactly where to start, I can recommend Tiller Money: https://tillerhq.com. Sometimes the best place to start is just "knowing where you stand". But there's lots of great tools for personal finance. Pick one and hop to it.

But there's no secret magic there, and I'm not even sure I'm doing anything different now that I shouldn't have already been doing 2 years ago. I may not have spent so much money... but that's a me problem not the "result of a recession" problem.

mr_tristan··on Ask HN: Do you ever truly use your revision history?
Git annotate is a fantastic tool, even if the developers aren't great contributors.

A lot of developers do not write good statements. They don't even link to a ticket. But you get to know those developers real quick when you're doing spelunking using annotate. And developers who don't write good commits probably didn't leave any other documentation behind of use.

I've used this to illuminate "technical debt" from a different perspective. If you take a critical code path, find the important commits for critical logic, and then just show the "context" you're left with, you'll often be able to say "this is why your quality sucks" in a real concrete way.

Managers love proof, and showing them what little context you have for critical areas can be a very different way of looking at the quality of their systems. Otherwise, I've often seen a LOT of overconfidence largely because "we have automation in place".

mr_tristan··on Signs you’re working in a feature factory (2016)
The problem is that "shipping stuff" is not what companies are supposed to be solving. They're supposed to be providing _value_ to customers and investors.

A "feature factory" model is bad because it masquerades as progress.

"Value" is harder to define, and often can't be measured _simply_ with metrics - you need metrics for insights, but most metrics are very much trailing indicators. Also there are lots of silly metrics like "tickets closed" that are easy, and naturally companies gravitate towards anything easy as the number of people rises. And factories love metrics.

mr_tristan··on Diagram as Code for prototyping cloud system architectures
I've used asciidoctor with it's diagram plugin (https://asciidoctor.org/docs/asciidoctor-diagram/) internally on memos/draft documentation, which that gives us an ability to actually just check in the asciidoc with diagram source into git. Then we use merge requests for a real review process. Then, I just usually just export to pdf or word for broader sharing among the masses. (Amazing how this usually gets far more attention than Confluence, etc)

Main benefit is that most of these kinds of CLI diagram tools have much longer lives than any GUI-based diagram software I've used.

But even just having a separate "diagram source" file where you just check in an image is still nice. Then you don't have to bother with wondering who has access to the tools, etc.

mr_tristan··on Pioneers vs. Process People
What makes me uncomfortable is tying my professional identity up with a part of the product lifecycle.

Sometimes it's just fun to take on risk, and other times, great to be able to eliminate risk. But fundamentally, almost everything in tech is a kind of wicked problem. Sometimes that problem domain sometimes shifts to areas where you have less control.

Where things usually go off the rails are when you feel like you're no longer making contributions. I find _this_ is really what "pioneer people" are really griping about. It isn't that they need to "move fast and break things" or other such BS. It's that they got used to having control and seeing the impact of their work. After a while, things become complicated, and it becomes hard to see how they make much of a difference.

Usually when I see one smart, inspired person leave because of "process", there's often a team left behind frequently spinning their wheels on something useless.

mr_tristan··on Monoliths Are the Future
Yeah, it sure seems like Maven, by design, tries to avoid dependency locking and version resolution configuration, but in turn, becomes kind of a bear to manage once you get fairly large.

I've switched to Gradle, and one of the first things I do is usually flip on dependency locking, and then even go so far to reject and/or flag anything that doesn't have a clear semantic version scheme.

Gradle's documentation can be a little overwhelming, but there's a lot more to these topics that developers usually overlook:

https://docs.gradle.org/current/userguide/dependency_locking... https://docs.gradle.org/current/userguide/resolution_rules.h...

Many companies would benefit from real dependency locking, and making sure they have reproducible builds. It's tricky, but, it can be a lot easier than "containerization", which I've often heard touted as a solution. (Containers are useful, but you should fix your CI separately.)

mr_tristan··on What sci-fi can tell us about the future
I had the exact similar thought: it's the way the touchscreens, voice interaction, and tactile systems melded together felt _intuitive_ instead of showy or glitzy.

While terminals were often just a basic touchscreen, many critical elements, like the chairs on the ships, had tactile input (joysticks, buttons, etc) - to deal with input under gravitational shifts.

It really gives everything a greater physicality.

mr_tristan··on What sci-fi can tell us about the future
This is the one aspect of The Expanse, the tv series, that I like a lot. One day, I'd actually think their terminal system would actually be a real thing:

https://www.forbes.com/sites/kevinmurnane/2017/03/08/science...

(Unfortunately, this would probably require public infrastructure, not private, which just seems to create more walled gardens. But... I digress...)

This approach to technology is really a major difference from the expanse and a lot of other sci-fi. FTA:

> The writers and creators of The Expanse take the view that technology develops over time to serve human needs but it doesn’t do away with those needs by either wholly satisfying them or destroying the people who have them. Technology advances but the human problems remain.

In many ways, a lot of sci-fi writes focuses on technology first, people second. And _that_ often resembles "concept products" that never see the light of day.

mr_tristan··on Just Build the Product
> I’ve never seen insurmountable technical debt grind business to a halt. Not once.

I’ve seen this happen more then once. The best and brightest tire of the crap and leave to go do other things; and those who stay erode the culture into a cesspool of negativity. Sure the business trods along for a while but often the products just enter a phase of slow death and irrelevancy. At some point there’s some kind of private equity acquisition or transaction which just temporarily delays the inevitable.

To be clear, I’m not arguing for “strict requirements”. Just that the professional engineer is who needs to distill the chaos into clear and ready action. And, that “just ship it” can sometimes come with cost.

These articles usually come across as flippant. They are written from a small business or early phase/unproven startup point of view. Sure, don’t waste all your time tweaking tools, but at the same time, make sure you’re not shooting yourself in the foot because of the 50 kludges put in place that overlooked security or performance considerations.

I guess this is just a way of saying “there is no silver bullet”. “Just ship it” doesn’t always work.

mr_tristan··on Oakland shows how to expand housing supply: tell developers they can build homes
I'm not sure what Oakland is doing is actually a major change. It's like something just triggered the money to flow to finish a bunch of projects in the east bay. But the spigot could just turn off again.

There's something broken in city planning that seems to be the largest hurdle to addressing affordability. Cities seem to want to have a box with a label on a map that doesn't change much. Then, if something changes within that box, there needs to be this big massive process. The "real fix" might be figuring out how cities can work on a smaller scale, not with these massive projects.

Just look at the report for the Oakland plan: https://cao-94612.s3.amazonaws.com/documents/FINAL_DOSP-Publ...

I'm struck by how much it must have cost to even generate that plan. And, there's a ton of goals, but no feedback loop. As the plans are implemented over the next decade or two, how do they know what's going well and what isn't?

mr_tristan··on Can gaming become the happy-hour for remote teams?
Honestly, I couldn't see it really working much more frequently with some functions and people spread out over timezones. It was common to not be able to meet up at for a week or two with some roles - sales would be traveling, too many issues, meetings. etc
mr_tristan··on Can gaming become the happy-hour for remote teams?
As a remote engineer these days, not sure a gaming session with my team is what I need on top of work. I do my own gaming, and have pretty different preferences from everyone else. We do physically get together 4x a year, which is honestly more then enough to develop strong social bonds.

One thing my company did for a while was a “random coffee chat”. You could opt in and get matched up with someone, and basically chat for 30 minutes about whatever once a month. This was awesome, because I actually met very different roles at the company, like sales engineers or the head of HR. Not exactly the “social time” of happy hour but almost more valuable

mr_tristan··on Deconstructing a Sexploitation Attack
I think it wasn't so much the normal text content of the PDF itself, but, attackers targeted specific media features of PDF readers that would open files or attachments within or linked from the PDF. Image attachments, etc.

Fun times: https://www.cvedetails.com/vulnerability-list/vendor_id-53/p...

mr_tristan··on One Man's Junk
Right, real big green logs were once used, but actually constructing a timber frame home requires quite a lot more skill for joinery than working with lumber, which is just nailed together. Timber framing is still around, but way, way less frequently used, since it's so expensive. It's awfully hard to work with large green wood that results in a safe structure.

Don't get me started on more modern engineered wood, e.g., plywood, or stuff like cross-laminated timber. You can create your own plywood pretty easily, but it is hardly a convenient process.

mr_tristan··on Gitlab considers not hiring SREs and Support Engineers in China and Russia
It's actually in the discussion:

> There is an unacceptably high risk that these nations may apply pressure to individuals living within their borders with sensitive data access (based their role at GitLab). It is our concern. And it is the stated concerns of several customers.

The discussion is actually pretty significant, as they sort out how they might manage the _customer demand_ that is creating these hiring blocks, and in turn, how that is reported and tracked.

I don't see this as a purely "done deal", it's a company having very important discussions in the open that most would just default to "restricted". All this transparency is a great source for others to learn from.

← PreviousPage 5 of 10Next →