joeldo
Why not just provide a clickable link given this is an article on the web?
Obviously bugs are inevitable, but why this wasn't progressively rolled out is beyond me.
The Graphql server itself is still publicly exposed to the internet, but the ability to query is not. Queries have to be whitelisted ahead of time (persisted queries).
Users generally have time to decide if the output ChatGPT provides is accurate and worth actioning.
You can add event listeners to the SVG's paths/groups and apply fill when clicked.
I've used both VSCode and Rider and I think both provide an enjoyable development experience.
Aside from VS only running on Windows, it doesn't feel like a second class experience at all to me.
I'm not saying you have to make the entire project open source, but if you are claiming it is an open source project it comes with the territory.
After perusing the Github repo, it looks like the actual editor logic is not open source (in fact it lives in a private repo which you control), and the linked repo is just a wrapper around it.
TypeScript for Java/C# Programmers
If it was the choice of language that drew you to apply, learning about it is not going to hurt!
- The entire housing market is ripe for disruption, especially if we don't want to see a lot of younger people living out of the back of cars or vans.
What kind of disruption are you referring to here? Policy level (I agree) or something else? Curious to hear your thoughts on this.
The result is that unless you are able to acquire funding, you result to trying to getting something built outside of your job, which is much more difficult to pull off successfully with the limited time available.
Ask HN: Are there senior devs who liked switching from static to dynamic typing?
I'm curious if there are any senior engineers who have swapped from using statically typed languages to dynamically typed languages later in their career and prefer this way of working?I've met many senior engineers (myself included) who have made the opposite transition (dynamic -> static) and now the thought of using a dynamic language for anything outside of small scripts is uncomfortable.
That definition is rarely as accessible as an explicit type though. For example take an API response or any third party library. Determining the data type isn't as quick as simply scanning a function for the object definition.
- Dynamically typed languages are very popular so it seems that many developers can work their way around dynamic typing.
As someone who has spent a fairly even mix of their career using typed/untyped languages, I think this is due to a few reasons:
- Lower initial learning curve.
- Lower barrier to entry.
Those are real benefits, but I would argue most projects quickly hit a point where they benefit from static analysis.
Having worked with 100s of devs at this point, I'm yet to meet one that after learning a typed language and using it for a sufficient period of time (more than a few months) wants to use an untyped language for anything outside of small scripts.
You've never worked with vaguely named variables? What you are suggesting is guessing the data type based off the name.
- What type of object? The type that can be added to a cart.
Okay sure, but what precisely is that?
- Nobody just throws random objects at a function.
I couldn't agree more - so the follow up question is what is the fastest way to get familiar with what type of input or output this function returns?
- They are familiar with the code in general and they know what to do.
For very small projects with very small teams after some onboarding time perhaps, but outside of this I would disagree.
Code changes over time, parts that you use to know intimately get changed subtley and erode knowledge away. Having types in place highlights these changes if your assumptions are incorrect.