thibauts

6 ms·

1.
by thibauts 5mo ago
« Don’t be evil »
2.
Naming Is Hard: Let's Do Better(youtube.com)
2 points by thibauts 2y ago|0 comments
3.
by thibauts 2y ago
The secret sauce will most likely be tight integration with Shortcuts, enabling the language interface to drive and automate existing apps.
4.
by thibauts 3y ago
I did exactly that with a custom GPT and it works pretty well. I did my best to push it to respond with its training knowledge about brand reputation and avoid searches. When it has to resort to searches I pushed it to use trusted product i
5.
by thibauts 3y ago
That was indeed a big parameter. We missed someone on the team able to connect to us to one or two large early adopters. We learned that building a good product and building a company selling it are two very different things !
6.
by thibauts 3y ago
Lack of traction basically. We ran out of time and money. Also we, maybe wrongly, did not feel like we could compete with the big ones without clustering. Yet we had a lot of fun building it. It was a thrill to see our product deliver perfo
7.
by thibauts 3y ago
Built something similar in Go with a friend a few years ago. https://github.com/thibauts/styx
8.
by thibauts 3y ago
That is my understanding also. I would very much like an expert answer on this one !
9.
by thibauts 3y ago
They make money because growth. Any strategy that is not based on information asymmetry or unique clever use of information makes less than the market on average.
10.
by thibauts 3y ago
You couldn’t feel that way if you had no doubt or did not care about your level or worth as a developer. So you do care about how others perceive your level and you are not totally convinced that your self evaluation is right. I would say d
11.
by thibauts 4y ago
It’s time we fork a « software design » category from the software engineering catchall. Yet many great suggestions on this topic but one is missing, which in my opinion sums up a lot of the software design classics : « The Design of Every
12.
by thibauts 4y ago
You can deploy your whole monolith on one single lambda and it will scale the same. It may even help to keep it hot. Services, micro or not are only really useful when load factors are vastly different and you’re not serverless. Or when you
13.
by thibauts 4y ago
Right. Then HTTP requests being share-nothing they horizontally scale in a single instance, too. Just spin more cores. This microservices craze has been mind-boggling. As for many other fashions, it’s excruciatingly difficult to make young
14.
by thibauts 4y ago
I wouldn’t call these talented.
15.
by thibauts 4y ago
Welcome to advertising driven journalism.
16.
by thibauts 5y ago
I call it wasting time trying to fit square pegs in round holes. Many things and approaches have their virtues and their place, be it top-down, bottom-up or tests. Silver bullet techniques and dogma have absolutely none.
17.
by thibauts 5y ago
Then it’s not test « driven ».
18.
by thibauts 5y ago
How does TDD force you to a better design ?
19.
by thibauts 5y ago
No. TDD is as top-down as it can be. « Test-driven development (TDD) is a software development process relying on software requirements being converted to test cases before software is fully developed, and tracking all software development
20.
by thibauts 5y ago
Used to use this cheat sheet https://scikit-learn.org/stable/tutorial/machine_learning_ma...
21.
by thibauts 5y ago
Here is an event stream abstraction that has very strong semantics (exactly once in most cases) with simple usage examples, native HTTP and websockets APIs, strong atomicity and durability guarantees [1]. What it doesn’t have is clustering
22.
by thibauts 5y ago
You’re right, I pushed it a bit too far. What I was feeling and trying to convey is how it flips the design process from bottom up to top down, by forcing the design of the interface first. From my experience you miss a lot by doing that. T
23.
by thibauts 5y ago
When tests amount to specs waterfall tends be be referred to as TDD.
24.
by thibauts 5y ago
Exactly this. Encoding business requirements or expected output of a complex algorithm by writing tests before code can make some sense. Writing tests for something that has no defined shape yet doesn’t.
25.
by thibauts 5y ago
You can move the code that hides behind the interfaces that you test, but you can’t redesign these interfaces which is the essence of design.
26.
by thibauts 5y ago
That’s right, but the WebSocket browser API is event driven so the browser HAS TO recv from the socket and dispatch a JS event as soon as data is available. You’ll get proper back pressure on websockets with synchronous clients that read me
27.
by thibauts 5y ago
What about a wire only linking the earbuds to each other and providing controls and a Bluetooth transmitter ?
28.
by thibauts 5y ago
This is my experience too. Millions of persisted and serialized TPS on regular NVMe with ms latency. Though it took a bit of effort to get to these numbers. https://github.com/dataptive/styx
29.
by thibauts 5y ago
I’ll be more than happy to get your feedback if you test it ! Especially potential shortcomings preventing its use in production settings.
30.
by thibauts 5y ago
Styx was built with this kind of use in mind, among other things. If you’re using Go you can even use the storage engine standalone. It’s pretty robust and very fast (millions of fsynced writes/sec). https://github.com/

More ›