thomasrognon

Come on, man. We're talking about classified information, not general OPSEC advice. I worked in a SCIF. Literally every piece of equipment, down to each ethernet cable, has a sticker with its authorized classification level. This system exists for a reason, like making it impossible to accidently leak information to an uncleared contact in your personal phone. What Hegseth did (and is doing?) is illegal. It doesn't even matter what app is used.

This describes my current situation so precisely. The only thing keeping me on is the engineers I brought in and the initiatives I'd like to finish. I'll probably "retire" early in a few months and work on passion projects.

You need

  "noUncheckedIndexedAccess": true

  type OddNumber = number & { __BRAND_ODD_NUMBER: true }

  OddNumber[]

  const isOddNumber = (x: unknown): x is OddNumber => typeof x === 'number' && x % 2 === 1

GCP still has domain management via Cloud DNS. That isn't going away. This is just domain registration. I say this as someone who uses Google Domains and GCP and is upset at this decision.

latakoo | Codec/GPU Engineer | Austin or REMOTE

We do video transfers and workflows. Our team is small and selective. We're looking for a meticulous and methodical engineer to develop a custom video codec. FFMPEG and GPU expertise is a huge plus. Comp is top of market.

Please email me directly (it's in my profile).

IPFS is decentralized storage and is a big part of what web3 is. Many NFTs use IPFS urls and many dapps are hosted on it. Browsers can resolve them today via centralized gateways like ipfs.io and some browsers (like Brave) support IPFS natively.

Mine has interesting spots and colors, I'm really curious why that is: https://viewer.legacysurvey.org/?ra=197.6961&dec=29.7091&lay...

https://www.cloudternal.com

It's like AirTable/Lists/etc but for big organizations.

So the focus is on a more useful permission system, handling lots of data, dead simple data entry for tech-phobic employees, and getting the information you need quickly (as opposed to spending time fiddling around with how data is displayed, this isn't an "app builder").

The intent is to replace the hundreds of untracked, out of sync, insecure Excel files being used as a database in most large orgs.

Cool tech note - people learn to use a graph database with Cloudternal, even if they never know what a graph is.

Let's be honest. The whole blockhain / cryptocurrency was never about that ever.

I'm not sure why you think this. "Banking the unbanked" was a huge Bitcoin mantra back in the day. If anything, it's disappeared more recently as speculation has taken over and the narrative has moved from "p2p cash" to "store of value".

Which is a bigger driver of decentralization? Running a node or adoption? I would think a universally adopted blockchain in the multi-TB would turn out more decentralized than a narrowly adopted multi-GB blockchain. # of potential business/research/government nodes >> hobby nodes.

Wasn't that a large part of Microsoft's strategy? I remember taking an "IT" class in high school in the early 00's that was 100% focused on learning MS Office. People bring what they know into the workplace.

The barriers, time, and cost for nuclear seem to be primarily of political origin, not technical. It's held to an unreasonable higher standard than anything else.

Although he says "able to compress our data", he means that the uncompressed representation is smaller. In addition to memory savings, iteration could theoretically be faster due to fewer missed branches (imagine iterating through mostly similar width characters vs iterating through characters of varying widths).

TypeScript is following JavaScript, not the other way around. Generally, ECMAScript proposals get added to TypeScript when they hit stage 3. Optional chaining and nullish coalescing were added to V8/Chrome and TypeScript around the same time.

For another data point, I immediately thought "that's a surprisingly good name!"

Or attach funding to each kid and let schools compete.

For scenarios where you want users to only see "their" data, managers to see their employees' data, and vps/admins to see all data are common scenarios that are often hard to implement in these tools.

This is exactly a major problem I'm solving with https://www.cloudternal.com. I would absolutely love to show it to you and get your feedback on it if you have time (my email is in my profile).

Hey there, I set that up. The request early access link is a Google Form so it was an issue somewhere between you and Google. It works for me now, but if it still doesn't work for you, please email Carey personally (email is in his HN profile).

It's MTailor (like a tailor) and I think they're great, but my dream is a bit different (elaborated in another comment).

I'm familiar, but MTailor is a standalone brand. I'm dreaming of a world where I can see any piece/brand of clothing and not even think about the size or fit. It's just taken as a given that I can see it on myself (AR?) and get one that fits me perfectly. The clothing outlets, last stalwarts of strip malls, would be a thing of the past. No such thing as needing to "try it on" anymore.

Everyone has different fitting issues. My main one is waist length/width and shoulder width. I'm 6'2" and fit so the waist of most shirts barely go below the top of my jeans and getting the shoulders to fit often means having a parachute around my waist. It looks dumb and clothing fit is extremely important to overall appearance. There's a lot of disruption to be had in this space.

Edit: to be slightly more clear, I'm thinking of technology to replacing the incumbent infrastructure/processes/consumer experience, as opposed to just creating a new specialty brand.

Doing this would require on-demand manufacturing with operational costs close to what currently exists. I can see how it could end up cheaper simply due to not making clothes that don't get sold. I'm sure there's a lot of waste currently.

It looks like someone is thinking about this at Amazon: https://qz.com/963381/amazon-amzn-has-patented-an-automated-...

Yeah, why does clothing still come in S/M/L? Why can't I order existing brands in styles 100% fitted to my unique body. Surely you can instantly measure shoulder/chest/waist width, torso/leg height, etc with technology like Xbox Kinect. And on-demand, custom clothing has to be solvable in 2020, right? So it's just a momentum/supply chain problem, like Netflix vs old guard?

My compile time went from seconds to minutes when I made a recursive immutable type (which I reverted of course). Overall, I still love typescript.

Edit for the curious, here's the monster type that caused such pathological build times...

  type ImmutablePrimitive = undefined | null | boolean | string | number | Function;
  export type Immutable<T> =
    T extends ImmutablePrimitive ? T :
    T extends [infer U]                                     ? readonly [Immutable<U>] :
    T extends [infer U, infer V]                            ? readonly [Immutable<U>, Immutable<V>] :
    T extends [infer U, infer V, infer X]                   ? readonly [Immutable<U>, Immutable<V>, Immutable<X>] :
    T extends [infer U, infer V, infer X, infer Y]          ? readonly [Immutable<U>, Immutable<V>, Immutable<X>, Immutable<Y>] :
    T extends [infer U, infer V, infer X, infer Y, infer Z] ? readonly [Immutable<U>, Immutable<V>, Immutable<X>, Immutable<Y>, Immutable<Z>] :
    T extends readonly [infer U]                                     ? readonly [Immutable<U>] :
    T extends readonly [infer U, infer V]                            ? readonly [Immutable<U>, Immutable<V>] :
    T extends readonly [infer U, infer V, infer X]                   ? readonly [Immutable<U>, Immutable<V>, Immutable<X>] :
    T extends readonly [infer U, infer V, infer X, infer Y]          ? readonly [Immutable<U>, Immutable<V>, Immutable<X>, Immutable<Y>] :
    T extends readonly [infer U, infer V, infer X, infer Y, infer Z] ? readonly [Immutable<U>, Immutable<V>, Immutable<X>, Immutable<Y>, Immutable<Z>] :
    T extends Array<infer U> ? ImmutableArray<U> :
    T extends ReadonlyArray<infer U> ? ImmutableArray<U> :
    T extends Map<infer K, infer V> ? ImmutableMap<K, V> :
    T extends ReadonlyMap<infer K, infer V> ? ImmutableMap<K, V> :
    T extends Set<infer M> ? ImmutableSet<M> :
    T extends ReadonlySet<infer M> ? ImmutableSet<M> :
    ImmutableObject<T>;
  type ImmutableArray<T> = ReadonlyArray<Immutable<T>>;
  type ImmutableMap<K, V> = ReadonlyMap<Immutable<K>, Immutable<V>>;
  type ImmutableSet<T> = ReadonlySet<Immutable<T>>;
  type ImmutableObject<T> = { readonly [K in keyof T]: Immutable<T[K]> };

I've been working on an enterprise SaaS startup and have the same challenges. Explaining a general purpose tool and new capabilities that no one has seen before is really daunting. I'd love to hear more about your experience and how it turned out, especially the sales side.

I'm working on a startup (https://www.cloudternal.com) in Austin. If you want to connect, my email is in my profile.

I use Cloud Run and nothing is specially developed for it, other than just being stateless. I can take my container and run it on a generic Linux box with zero changes (in fact, I run it in WSL2 on my Windows machine all the time). And I just install the normal Node.js, imagemagick, etc in my Dockerfile, no special builds or flags.

I really like this idea. I already planned on enabling users to upload thumbnails images for the "book cover" of a table. I could make each tab's favicon based on that.

We don't currently have automation, but we plan on having it ready either Q3 or Q4 this year (we might do mobile first, it depends on demand). Thanks for signing up, we'll reach out to you soon!

I think there's so much truth to UX being king, especially for tight-knit forward-thinking teams. However, these products always seem to ignore heavy use cases common in large orgs. Like lots of records and nuanced permissions that really fit business rules. I started from that direction with https://www.cloudternal.com (and will have a great UX eventually too!).