tinkertamper

I'm curious about what you mean here. It sounds like you're saying that applications shouldn't concern themselves with consistency. Can you elaborate?

Love this!

Call me lame, but are there any open-source projects that accomplish this type of gui in typescript? I have an idea but it uses something written in JavaScript.

I created a sub 9 years ago that now has a few million subscribers (so now requires a bit more effort to mod). I _don’t_ get paid, though I certainty wouldn’t turn it down. I started the sub because I like the content that is posted and I want to continue seeing more of it. Why continue to mod? Because I like to be involved and keep this little square of the internet free of toxic and often hateful spam/content.

> It seems threatening to take it away is making them compromise on their values quite effectively.

What exactly are you referring to here? I see this narrative in a lot of places and I’m confused about what “values” mods supposedly collectively have? So much discussion online paints moderators as some sort of a connected cabal with alternative motives instead of unrelated nerds who enjoy niche content.

I was hoping this was about my coworkers tuning on our cloudwatch alarms until pagerduty stops calling

That’s not really a fair comparison here — A more fitting metaphor would be whether or not you could intervene on assembly code not knowing assembly.

This is just what was just called “speaking tech” back in the early 2000. I see a lot of discussion online about “prompt engineers” or “ai whispers” as you put, but I think the reality is that these tools are just another UI paradigm that our current generation will (on the whole) struggle with and the next generation will find intuitive.

An IDE that provides a linear view of your code base. Follow code paths as though they were all inline, e.g. expand views of function/method internals inside the calling function, etc. No more changing files/modules.

Before you wax poetic about this period, please read more on the complete disregard for the families and communities impacted by the large construction projects from that time. Replies comparing the US today to China would also benefit from the same. Public works has a lot of issues with cost and inefficiencies, but I think we should all be happy that eminent domain is not wielded with the same disregard for human life as it once was.

100%, this is exactly where my head is at too.

I used to have a boss who’d ask me to rate my company satisfaction with the company 1-10 at every 1:1. This always struck me as one of the laziest/misguided management moves I’ve encountered, and I’m sure he felt it was both accurate and clever. If you manage people, and don’t understand that basic power dynamics will always trump encouragements for “openness”, you are naive at best and willfully blind at worst.

There’s also a playground to play with modeling and typing here: https://electrodb.fun

Modeling, and actually implementing, single table design for DynamoDB has a lot of pitfalls and boilerplate. I wanted to make it easy and fast to define models and implement collections of models to get more out of a single query without scans. Having your entities dynamically infer typing from the model (without having to manually generate typedefs) is also huge win for usability and dx.

Ok, it’s clear where you stand. I’m not here to be negative, only to share with folks interested in the product that they are significantly back logged. Hopefully everyone knows what the means in a Kickstarter context. Their marketing is great, the jury is still out on their actual product.

Let me put it this way, I was backer #816. They currently have 37,987 backers. They raised $4,882,784 during a global pandemic. I think I’m not off base when I said “If you can get one.”

If you can get one. Ordered mine last April, still don’t have it, no sign of getting it, and they don’t respond to email/Twitter. I’ve given up.

Had a Product Manager who would always ask for Y, but had ego issues and would shut down when asked for context, examples, or client problem statements. Too many times we built Y then we had to face the consequences of not building X when put in front of customers. Very frustrating.

Fintech doesn’t have anything against node, institutional banking are the ones where old habits die hard.

I bring up Maslow a lot at work, I think it’s one of the few things I enjoyed from my partial business degree. What’s missing from this article is the context of the release, project, company etc. Some project environments don’t allow for the proper time to get the things done “properly”. Some product managers don’t have a clear enough vision or handle on the details to allow developers to know what “correct” really is.

If the team, project, company or whatever is not in a good place you can never really hit these higher “levels”; you’ll never reach the next rung on the pyramid if the context it’s built on is still at a lower one.

> I'm surprised to hear people keep re-learning this lesson. Back when web forums were popular, this was basically the one big mistake I kept seeing people make. Way too much compartmentalization.

Ahh yes, the “General” section of phpBB. To be fair though a whole generation as come online since then, that never had an opportunity to learn for themselves yet. The internet itself moving away from small niche sites/forums to subreddits/groups/categories under big monoliths.

I can understand this concern though I can assure you when I say "culture fit" I'm considering it a two way street.

A good example: I had an interview earlier this week for a full-stack role and the inteviewee had recently come off a two year project that was heavy on react. The project he'd be on has a jquery frontend. I told him candidly that the project would likely never make a "modern" refactor a priority, and asked him if he could still be happy in a role that used jquery.

Our full-time team is small and ensuring we can all collaborate and work together is very important for us to be effective. On the flip side we try to be transparent about what our team looks like too and give you a chance to decide if you could be locked in a room, hashing out which circle talks to which on a whiteboard, with us.

Recently I started trying something new for our interviews. I start with a phone interview that is more about discussing their background, expertise, what they need to feel productive, and explain the role. If I think they’d be a good culture and expertise fit, I send them something like this (I’ve made a few): https://gist.github.com/tywalch/cf60e4c942ab6a80e481f4ba6754....

It’s a small “api service” that represents a POC with some bugs and bad practices. I tell them to look over it, write down notes on how to make it production ready, setup a time to discuss their thoughts in a second call. No code writing necessary.

It ends up being an excellent Rorschach test where folks can really show/express their unique skill sets and experience. I ultimately let them drive the conversation and it gives me great insights into what experiences have shaped their career and what it might be like to collaborate with them. Best of all it does resemble what some of their day to day might look like better than hand crafting some tree algorithm.

“The HTML is totally wrong and exceedingly verbose” is not exactly something someone who used frontpage cared about.

I mean in the early 2000s there was MySpace, LiveJournal, Blogger, etc. That’s not all that different from Facebook, Medium, Tumblr in the way you’re saying. Those older platforms were way more customizable though, and frontpage definitely helped. You also had sites like geocities and angelfire that got a lot of non technical people interested in making websites.

I hear this argument a lot but I think it is exactly OPs point when he says, “The market can’t act against what it can’t see”.

Your average consumer doesn’t know the extent of what they’re trading. Take Facebook, even with high profile stories and documentaries it’s reasonable for your average consumer to assume that what Facebook tracks about them is what they actively give to Facebook themselves.

I’ve had conversations with people that say, “I rarely even post on Facebook” and “If they want to monitor pictures of my food/dog/etc whatever who cares”, without any solid understanding of what even having the app installed alone is giving Facebook.

But then how will developers exert their local domain dominance to imply and an even greater breadth of knowledge when patronizing other devs? /s

I see this criticism a lot for serverless but I don’t see it in reality. Serverless is still just running code, the only part that wouldn’t be portable is the entrypoint data structure which is amounts to practically nothing.

I’ve found returning a tuple with my validation functions to be very helpful.

  let [isValid, err] = validate(data)

It’s nice for a few reasons:

1. I know anything returned `err` is safe to display back to the user

2. Using the array (as opposed to an object) can allow me to name the values when I destructure so it can be used multiple times in the same block with useful naming.

3. I can destructure just the first half `[isValid]` if that’s all I care about.

4. More generally it helps keep the code readable. Other control flows might rely on some casting, assumptions, or exceptions but this way presents a nice customizable api for users writing the code, and a readable api for those reviewing the code.

I’ll probably catch a lot of flack but a lot of criticism in these comments for the author who finished something. It’s easy to sit in the cheap seats and cast stones, but this guy made something that works, and you can always make your own if you know better without tearing down the work of others.

What is that based on? Anecdotally the folks around me right now agree a common flow is:

1. See hn link.

2. Go directly to comments.

3. Top comment is seen as counter argument to the article.

4. Discuss on premise defined by top comment (not article).

Unless there’s a way to safe for sure (ex HN weighs in with analytic data) it’s all speculation.