913 karma · joined September 23, 2009
In her case, the target language is Spanish, so she does courses from Domestika: https://www.domestika.org/
Or whether the function accepts naked types as parameters or error unions!
The debug namespace is indeed the right place for a wholly generic print. The first day I took Zig out for a spin, std.debug.warn briefly confused me by eating errors and printing their name instead of (as I expected for a short minute) giving a runtime error.
This is a good design decision for the debug namespace, but you don't want a regular call to print() to take an unwrapped error without complaint!
1. The system that gives a service to the public is publicly accessible by default. The system that rotates its credentials it doesn't need to be; it can sit behind your firewall listening only on one port for ssh, with firewall rules allowing access only from a bastion host.
2. The credential rotator also connects to your server and drops credentials into it; you don't call from your server to the credentials rotator, because see Point 1 above. This limits the attack surface.
You're right that everything is potentially vulnerable, and so would the credential rotator system. However, by rotating secrets this way, you shift the locus of security to a smaller place that you can defend much better.
The linked comment recommends using strict/eager fold-left instead (`foldl'` in Haskell) of using lazy fold-left (`foldl`, with no trailing apostrophe). It's not saying that you shouldn't use fold-left in any language.
Reading the HN title alone, in its front-page context, it looks like it's saying that it's the fold-left generic operation that's wrong for lists, and not just `foldl`, Haskell's default lazy implementation of fold-left. Paradoxically, following the guidelines and re-using a boiled-down version of the linked comment's first line results in the line being misleading and/or link-bait (I guessed what it was about, but I still had to go and check).
For some time I've thought that the HN policy of disallowing editing of post titles, while correct, can be taken too far, and that many titles would be better with some annotation.
In this case, "It never makes sense to use [lazy] foldl on lists [in Haskell, use foldl' instead]" would be a better title. A bit awkward and maybe inelegant, but it says what the article means. Out of its original context, the HN title doesn't say what the posted article means.
Maybe "Lazy foldl versus strict foldl' in Haskell" would have been an even better title, if the guidelines allow for using one's discretion on when to disregard them.
Other common case is that of headlines in the first person: "My X ..." would often be improved by editing it to "[Name's] X ..." or "[Name of whatever X is] ..." while leaving it otherwise unchanged.
--
I don't know if @sama will get summoned to this comment like he would if this were Twitter, but it doesn't hurt to try.
They could also offer a SDK so apps could publish high utility info with low update frequency on the case itself: weather, public transport realtime schedules, etc.
(Edit: had originally written "low-latency" instead of "with low update frequency", because of the strong conditioning to associate "low latency == good")
They also wrote a software-based Z-buffer implementation. And a custom compression system that allowed vertex-based animation. And scene streaming from disc. And...
https://all-things-andy-gavin.com/2011/02/02/making-crash-ba...
Previously: https://news.ycombinator.com/item?id=9278082
The adverb "dónde" already has the preposition "de" embeded in it, as it comes from a condensation of Vulgar Latin "de unde", already meaning "from where". But Latin "unde" already is a composed form meaning "from where", and where the "-de" ending is not the preposition "de" but it's still a particle making "unde" a composed form...
So if you're Spanish and ask "¿De dónde?" you're asking
¿(from (from (where from)))?
Check out dependent type systems. These allow you to define, mindbreakingly enough, types that __depend on the values you assign at runtime__, and functions whose type depends on the values passed as arguments.
Don't ask me how it's done; it's all dark magic to me. All I know is that people who use dependent type systems claim they are very good at certain uses involving incoming streams of unknown data, like parsing binary protocols.
Sorry I can't help further.
Extremely same, but with Vue instead of React. In the last project I worked on, XState was a late addition, so it didn't control the whole application, but the part I wrote in it was bug free from the start.
My plan for any future JS/frontend project is to design the whole application's business logic around XState, and use Vue/React/Svelte/Whatever just for the rendering part.
> And Greene's 48 Laws of Power is practically a manual of sociopathy.
Exactly this.
https://en.wikipedia.org/wiki/Oracle_America,_Inc._v._Google....
And Krishamurthi's definition is the clearer I've seen that doesn't include "memoized recursion" as a subset of Dynamic Programming.
Shriram Krishnamurthi explains it best:
https://blog.racket-lang.org/2012/08/dynamic-programming-ver...
Do you use excel for anything at all? Whatever it is, you could start by building that.
- Do you put data into a spreadsheet and then email it to someone else? Make a web app where you put in the data using your account, and the someone else can view the data using your account.
- Do you have different spreadsheets with separate data than then gets aggregated/summarised manually into a single spreadsheet? That's a job for a computer program, not a person, and you can add that as a feature for your web application.
- Once you've done that, you have a website that can work with the new data, but some people will want it on spreadsheets, not on the website, so write a spreadsheet export/download feature.
- All your new data is in the website, but the old one is still in excel spreadsheets on your hard drive. Write an importer to read the spreadsheet data into your application.
- Is some of the data for your lab in a format that's also machine readable (barcode format?). Add to your app support for reading barcodes, either via phone cameras or laptop webcams: https://github.com/serratus/quaggaJS
I could go on, but I guess you know your next step better than I would.
A recommendation is also that you do all your development at home, not on company time, and not using any company resources. A lot of profitable business are website implementations of existing spreadsheet workflows. In the past three years, I've worked on two such applications, three if you count a physical device UI where the prototype UI was developed on Excel + Visual Basic.