👨🔬 Hey #dotnet folks, do you have secrets you'd like to share with the world? How about doing it on the #JetBrains stage? Submit your talk to be considered as a presenter for the #JetBrainsDotNetDays event. You can submit up to 3 talks to be considered.
WireMock is a very cool plugin for #JetBrains IDEs. It lets you mock HTTP endpoints with ease. Great when mocking up a sample app or trying things out.
📢 Hey, #dotnet folks! We are accepting presentations for #JetBrains .NET Days 2024. This is always a fun event, and you can submit talks of 30, 45, or 60 minutes.
As a presenter, you're not alone. We're here to support you every step of the way. You'll receive assistance from our team (including me and other advocates) to prep your talk, do dry runs, and receive feedback before the big day.
I’m hosting Chris Simon on a #JetBrains#livestream to discuss #TDD, #DDD, and #csharp. Not to be confused with D&D, which is about wizards, dragons, and dungeon masters… wait it's pretty similar.
I'm about to go live with Brent Roose of #JetBrains for his podcast, talking about the new #PHP Property Hooks RFC, the RFC process, improving PHP, and all that stuff.
They use #OpenAI, which means my GitHub OSS has almost certainly been used in training data.
They rely on OpenAI's promise to not ingest any code that is used for "context".
They specifically do not disclaim that their tool could result in me violating someone else's copyright, and they could suggest the same code to someone else, too.
Uninstall this crap, now. It's dangerous and irresponsible
I had fun making these sketches for a #godotengine tutorial I'm writing for the #JetBrains guide. I think they came out pretty good. What do you folks think? #dotnet#gamedev
Man! Really wish I'd made the effort to move to #JetBrains Rider sooner.
The speed of its TypeScript suggestions is soooo much faster than VS Code, and it doesn't constantly fail to resolve them. The amount of times I had to close and reopen VS Code to get it to work was ridiculous.
Normally I would not share ads, but our new #JetBrains video came out amazing. Lots of work from so many teams, but I very much like the vibe of the result. What do you say? https://www.youtube.com/watch?v=QGIBuhIRtQ0
After years of writing code in a solution, you open it and realize you now have to run a marathon through lax code maintenance practices, issues, and errors you didn't even realize you had.
But you have to start at some point, and what better time than now? A journey of a thousand miles starts with a single step.
Today I learned that apparently #JetBrains is OK with using pre-release quality software in production.
How do I know? Look into Dokka, their documentation engine. The main format is in beta. They also talk up Markdown and Javadoc, but guess what? Those are in alpha and they even say 'use at your own risk'.
Maybe it's just me, but if something isn't production-ready, it shouldn't be mentioned in your tutorials.
A reminder for all the web developers out there: Not every visitor to your site is on a high speed fibre connection!
I'm currently in Africa, so sending 115 requests and downloading 13.5 MB for a simple Issue Tracker (hello #JetBrains) takes a significant amount of time, and is really a bit over the top.
I like the idea behind the new sticky lines feature that #jetbrains released for #phpstorm - but I wish I could toggle which types of information I want sticking.
Having the namespace sticking is just sort of eating up a usable line for me.
It's release day at #JetBrains with lots of cool features including (entirely local) full line code completion!
You can check out 3min video to learn more about it and then go try it out and let me know what you think! It's exactly what it sounds like! https://youtu.be/DLBiJ5kYUFg
My god, adding a conditional breakpoint in #Jetbrains#Rider (and I assume other editors) and #DotNet makes things slow.
I only have 20k pieces of data (admittedly large individual pieces, but still), and I went from finishing the run in about fifteen seconds to waiting for five minutes before I hit my breakpoint.
This isn't me complaining about anything, just kind of wild that adding a single "Does this int equal this int?" adds so much overhead! I had time to type this whole post!