storafrid

6 ms·

1.
by storafrid 9mo ago
A blog post about GraphQL in an enterprise setting, that fails to address the biggest GQL feature for enterprises. Not unlike most material on HN about microservices. Federated supergraph is the killer feature imo.
2.
by storafrid 1y ago
Think half an abstraction layer higher. You're on the right track with multiple PHP virtual runtimes on a single VM - that could conceptually be viewed as a sort of precursor to function runtimes. The serverless function has higher-ord
3.
by storafrid 2y ago
Do you mean figuratively that OP is replacing Cobol? Because I don't see that in the article. It mentions other technology that I would not associate with a super-conservative stack - like Databricks, JSON, Postgres and Google Analytic
4.
by storafrid 2y ago
Yes, but I'm surprised that they attribute "cutting-edge" to Lambda. It's about as old as Docker.
5.
by storafrid 2y ago
Hi, thanks for sharing. A question: What is the advantage of this approach compared to the tool I'm using right now - continue.dev ?
6.
by storafrid 2y ago
I don't agree that it's useless either, but I would expect the test macro to match what I do while working: Opening multiple PRs in new tabs all the time, cloud vendor portal tabs, looking through logs and metrics, scrolling (more
7.
by storafrid 2y ago
Is this an LLM? :) The question was rhetorical. Both of these proposals have problems. But the main issue is that the author of the article is missing an angle of toasts as a UX concept.
8.
by storafrid 2y ago
The solutions seem to rely on a user that doesn't navigate before the action is completed. Does he propose locking the UI in the meantime, or to optimistically show the user a success result?
9.
by storafrid 2y ago
I hope the automatic price offset is separated out and labeled in the cart/checkout as "Apple's user fee".
10.
by storafrid 2y ago
Sorry, something was probably lost in interpretation. You wrote: > RTO for giants is a must because they die without the office. Are you referring to tech giants here? That's what the thread was about I believe (interviewing for tec
11.
by storafrid 2y ago
I pointed out the lack of description of those incentives.
12.
by storafrid 2y ago
They don't want to hire someone who knows Pandas specifically. They want someone who can identify this technology, learn it and then possibly implement it. And more importantly - someone who can do the same when the situation calls for
13.
by storafrid 2y ago
Do you mean that there is a secret quarterly meeting where Starbucks are lobbying RTO policy to Apple in order for "us big sharks to thrive"?
14.
by storafrid 2y ago
The wide range of offers you received may not necessarily reflect a "crapshoot" in tech hiring. Instead, it likely demonstrates the diverse needs, prioritizations, resources, and role definitions across different companies. Especi
15.
by storafrid 2y ago
Sorry I probably used the wrong term, not a native English speaker. I didn't mean lack of complexity or lack of "features" but rather the lack of carefully thought-through feature "depth". Like, we can infer generic
16.
by storafrid 2y ago
Certainly advanced, but not mature in my experience. Using e.g. classes and inferred generic function arguments, quickly reveals a lot of features that are missing. Often some similar feature is present but it lacks depth/completeness.
17.
by storafrid 2y ago
I have mixed feelings about this. While I do use TS with Node.js today and absolutely like the concept, its type system is still far from something mature and stable like C#. We keep running into ceilings (EDIT: lack of completeness/de
18.
by storafrid 2y ago
How many underlying services and clients was the GQL layer catering to? How many different digital products and independent teams? You referred to "the backend team" (one) and did not mention stitching/federation. This makes
19.
by storafrid 2y ago
Silly. Many big corporations trust Microsoft touching their code. There are enterprise policy controls for Copilot, which includes data privacy. If you want to make this argument, then the realistic reason would be that Copilot hasn't
20.
by storafrid 2y ago
I was writing SPAs with jQuery in 2008. By then they were already well-established. We used UI component libraries (mostly custom) on frontend and AJAX for server updates in XML/JSON format. They were hard to build compared to today, b
21.
by storafrid 3y ago
Yeah right, "Just the Facts". With text like this: "I am willing to outright say that ... the removal was ... massively botched."
22.
by storafrid 5y ago
Replacing Google Photos with hard drives? What. And replacing Google Drive with a client-based sync tool...? Maybe too high expectations but I was hoping for some level of similar functionality. Would be interesting to get advice on how an
23.
by storafrid 6y ago
Source confirming your statement, please, that Tegnell has been "wrong about almost everything". Because that is false and this is not Reddit. In my opinion he _lacks_ charisma. He's just a scientist. Which is good.
24.
by storafrid 6y ago
Lots of bashing here. Please provide clear examples, based on facts. I'm not very interested in how complex you think serverless architecture seems to be. Instead, let us know: What did you try, what was the aim, why did you choose ser
25.
by storafrid 7y ago
"Terms of use" returns 404, which I find bit funny for a service in a gray zone
26.
by storafrid 8y ago
I felt there was so much potential for that movie! The plot in e.g. AC2 is intricate. It's easy to stand on the sideline of course — I understand that this stuff is really hard to get right. It obviously is. But in my opinion, an actua
27.
by storafrid 9y ago
How would you define "overvalued"? Is it the current average price compared to a very low price three months from now? What if it recovers a few weeks after that — would that change the fact that it was once "overvalued"
28.
by storafrid 9y ago
I still have my reading list from when I started out with React. Here are some of the most valuable resources that helped me grok React: http://krasimirtsonev.com/blog/article/react-js-in-design-pa... http:/
29.
by storafrid 9y ago
If the company finds a person that they want to recruit, and that person happen to live in a high-cost location, they will need to pay up in order for the recruitment to happen. The only alternative would be to offer relocation to a lower-c
30.
by storafrid 10y ago
I'm not hearing a counter-argument. The company needs to get good people to work for them. And this is a way of getting someone from a high-cost location to work for them. If the location's higher living expenses aren't cover

More ›