Je vous remercie d'avoir regardé le podcast de l'Exception Unhandled.
Je suis Dan Clark, et c'est épisode 53.
Aujourd'hui, je suis jointé par Mathias Jost et Tim Caddenback.
Nous allons parler de notre nouvelle initiative de communauté.
Nous avons créé une nouvelle chaîne de chansons.



Nous sommes dotnet.
C'est une nouvelle chaîne, nous avons eu un épisode.
C'est cool de voir comment on s'en va aujourd'hui.
Ce sont toujours des bonnes.
Vous pouvez vous interpréter à l'écart de la liste et vous dire un peu de ce que vous faites.
Peut-être que nous ne sommes pas dotnet, car nous pouvons parler de ça.
C'est partie de l'épisode.
Je pense que Tim, vous êtes sur le top de ma maitre, les webcams.
Donc, au-delà de la première.
Oui, je peux, totalement.
Je m'appelle Tim Caddenback.
Je travaille pour DeepEle en Gérminie.
Je suis le seul developer d'Angleterre pour DeepEle maintenant.
Je travaille avec la communauté API.
Je suis une partie 3ère, je suis en train de construire quelque chose d'une partie d'ApI DeepEle.
Je suis aussi un MEP Microsoft, depuis mon deuxième année.
Je suis un développeur depuis 25 ans, à peu près.
C'est la plupart des temps dans l'environnement Microsoft.
C'est très bien, c'est une très longue période.
Comment vous le faites?
Je m'appelle Mathias Joost.
Je travaille pour une compagnie qui s'appelle InkTest.
C'est dans la Lair de Switzerland.
Nous travaillons avec les applications web, SQL et ASP.NET,
pour qu'on puisse produire des solutions pour des services de taxe,
des informations sur les entreprises et des autres marchés.
Je travaille aussi dans d'autres secteurs,
à la fin de ma vie, comme l'application d'embêtement.
J'ai travaillé avec C, pour exemple.
Mais aujourd'hui, je suis concentré sur les dot-net.
C'est très cool.
Avant de nous faire un tour de la Lair,
je vais faire ce épisode, je vais vous le dire.
Ceci va au Buxchley, je ne sais pas le nom réel,
mais c'est en masterdone.
Il a tweeté ou tout-tout,
je ne sais pas ce que le terme est en masterdone.
Dan et Ian, je viens de faire un podcast pour la première fois.
J'ai vraiment aimé ce épisode,
et ça m'a aidé à affirmer des concepts
que nous ferons de retour à ma travail.
Merci.
Il a réveillé un épisode 51,
qui était deux épisodes,
où j'ai été connu par Ian Cooper
pour parler de son library.
Si vous voulez en parler,
vous pouvez envoyer un tweet,
ou un tweet,
tout le feedback est très apprécié.
Je suis dracke,
c'est D-R-A-C-A-N.
Normalement,
je n'ai pas mentionné le chanel,
mais nous avons un peu de change,
je vais en parler au Discord.
Si vous vous rendez au site
unhandledexceptionpodcast.com,
vous verrez un lien au service Discord.
C'est très beau pour voir ça se produire,
j'espère vous le verrez.
Et bien sûr,
ce podcast est sponsorisé par Everstack,
qui est mon propre company,
qui a la capacité d'appliquer
et d'accompagner des services de consultation.
Nous sommes dotnet.
Qu'est-ce que nous sommes dotnet ?
Je sais,
mais je sais pas ce que l'on a fait.
Vous êtes partage de ça déjà ?
Peut-être que je peux commencer
avec le début.
En avril 2022,
je dirais que c'était le début,
parce que c'était un petit
repos de github, juste avec les créatifs de contenus
listés.
Et à ce moment, c'était
l'idée de
lister tous les créatifs de contenus,
les avoir sortis par le pays,
pour les faire découvrir.
Et donc,
le repos de github
a été un peu créé,
et a atteint environ 1 000 stars.
Et puis,
il a eu un peu d'interesse,
et puis, un jour, Tim m'a appris.
Et on a commencé
de parler.
Exactement.
Je suis assez proche
de les choses.
On peut commencer un blog,
ou commencer un canal de vidéo,
ou quelque chose.
Ce qui a commencé est très difficile.
C'est vraiment impossible de
faire un audience à l'heure,
parce que tous les mécanismes
derrière les Twitter, Twitter,
et tout le monde sont très, très difficile.
Et on a même remarqué que,
dans les groupes de LinkedIn,
c'est difficile de voir les gens,
même dans un groupe clos, c'est difficile
de faire des choses listées.
Et aussi, je me suis rendu un couple
des créatifs de net-contact déjà,
mais ici et là, tu as été
assemblé par quelqu'un d'autre,
et tu as été inquiétant,
et tu as vu cet homme avant, ça m'a vraiment aidé.
Donc, j'ai voulu
avoir une plateforme commune
pour le contenu de net,
qui ne fait pas de différence
si quelqu'un est un créateur
avec une expérience de 25 ans,
et que l'un des followers de 100K
ou quelqu'un qui a commencé,
ça devrait faire de différence,
car le contenu peut être bien aussi.
Et je me souviens
que le liste de Matthias a créé
plus tard, et je me souviens
que c'est la meilleure combination,
car nous avons déjà un liste de créatifs,
et je peux le faire dans une plateforme web.
Et là, on est, je pense,
un mois plus tard,
nous avons 140 créatifs
listés, nous avons plus de 1000
personnes qui ont déjà signé sur la plateforme,
c'est une excellente journée.
Donc, on est là.
C'est très impressionnant.
Je me souviens quand Mathias a commencé
de twitterer sur son GitHub,
et, comme vous le dites,
c'était juste un liste de créatifs.
Et ça a été...
J'ai vu beaucoup de tweets et des choses
sur ça, donc ça a été très populaire, très rapidement.
Et maintenant, c'est évidemment
de l'intérêt de WeR.NET, qui est assez cool.
Envers de l'interesse,
quel est le nom de WeR.NET ?
Je n'ai pas... Je suis venu avec le nom,
mais je ne m'en souviens pas.
En fait, je le fais.
Je suis maintenant en train de travailler
sur l'application de WeR Developers Conference
en Berlin.
Donc, je suis en train de
dire que nous sommes...
Je me suis dit pour une raison,
WeR.NET est assez cool,
parce que ça inclut tout le monde
dans de nombreux moyens.
Et la communauté est ce qui
fait WeR.NET, comme tout le monde,
évidemment, mais aussi tout le contenu
de créateurs, tout les gens
avec l'open source et le field.
Et pour avoir quelque chose, comme une plateforme commune
et dire qu'on est WeR.NET, et que nous sommes tous
sous la plateforme commune,
ça fait du sens.
Et c'est un grand brand, après tout,
oui, c'est vrai.
J'ai vu que tu as quelqu'un créé un mobile
ou un Mawip aussi.
Oui, c'est Gabriel,
je ne sais pas son nom de famille.
Je suis en train de parler avec James Montemagno
de la communauté de WeR.NET,
j'ai rencontré il y a un couple de temps
sur les conférences, et on a juste
parlé, et je lui ai dit
qu'il a parlé de WeR.NET,
et il a mentionné le projet
de planète de summary,
qui est un peu similaire,
ils ont agréé des feux
de la planète de summary.
Ils ont seulement agréé les feux,
ils n'ont pas fait des feux,
ils ont juste eu un FSS,
qui a combiné tous les feux.
Et puis, je lui ai dit
qu'il était comme, oui,
ils avaient l'idée de planète
de planète, ils n'ont jamais fait ça,
et maintenant, on a sorti de la tête
et on a fait tout ça, et il a dit
qu'il n'y a pas de point
de construire une planète de planète,
si on a ça déjà, il a dit
qu'on peut prendre l'envers de la planète de summary,
et qu'on peut mettre tous les autres
autorités sur WeR.NET,
qui a déjà été fait, donc si on va
au secteur de la planète de summary,
c'est l'une des plus grandes secteurs
que nous avons, je pense, maintenant.
Et puis, Gérard, il est aussi un employeur Microsoft,
mais il est part de la team de planète de summary
avec un app, il est cool.
Et maintenant, il a fait
un progrès fou, il était
comme, je suis joué avec ça pour 30 minutes,
on va voir comment je le vois, et maintenant, il ne peut pas
faire du travail, et il est en train de
faire des choses, et il a déjà l'air vraiment sympa.
C'est génial, je pense que j'ai vu un tweet
d'aujourd'hui, qui dit, il est progressant bien,
mais il a voulu que c'était un design,
ou un design qui s'est fait.
C'est très cool, c'est très sympa
d'avoir le tout productivité avec Maui,
et il a fait des choses très très vite.
C'est fou, c'est un truc
que je n'aime pas
de la plateforme, parce que c'est
designé par un développeur, et vous pouvez voir
ça, dans
beaucoup d'or, je ne suis pas
un design, pas tout le monde.
Il a bien regardé, le brand est sympa,
Mathias a été avec le logo,
et ça a vraiment bien regardé,
il a bien regardé, mais avoir
un peu d'input de un vrai design
peut peut-être aider un peu.
C'est cool, il a eu
James Montemagno en bord,
quelques ans plus tard,
parce que j'ai vu un donner d'Oxford,
et il a
en point de lui dire que
il est en train de faire un talk
d'un donner d'Oxford, en Europe,
et lui aussi, il est intéressé,
donc il a en fait jumpé sur le repos,
et en fait, je pense que c'est Clifford Agius
qui a été sur le podcast avant, qui
m'a mentionné un tweet,
donc il a jumped sur le repos,
et parce que c'est Oxford, il a dit
oh, je n'ai jamais été au Oxford,
c'est un peu bien, il a fini de parler en parlant de notre groupe de utilisateurs.
C'était vraiment surreal, avoir un café avec lui avant 100 ans.
Je suis vraiment dans un café, en faisant un café,
en chassant avec James Montemagno,
donc j'ai un imposteur qui a vraiment été très proche.
C'est un très bon gars, j'ai rencontré il,
et on a went to the.net developer days in Warsaw last year.
Il était là comme speaker,
et also Scott Hunter was there,
et a couple of other people,
and it was really, really awesome,
and talking to all these guys is always fun.
James is such a good speakers,
because when he was speaking at Donnerd Oxford,
his whole talk,
like I edit this podcast quite heavily,
but his whole speech was as if it had been edited,
but in real life,
because he was just like no thumbs and aars to completely clear,
just you can tell he's a very practiced speaker.
I'm very jealous.
Yeah, I can't do that either.
Every time I do a talk,
I'm like, I'm look at the recording of the talk
and like every time I'm going crazy about myself,
like what did you do there and what did you do?
Like constantly,
like, ah, and it's weird.
I don't like myself speaking,
but people like it.
I don't know.
Well, I get rid of all those for the podcast,
so hopefully be happy listening back.
So you mentioned,
well, I mentioned Mastodon before in the intro,
and I know you've got a good community on Twitter.
Have you got any presence on Mastodon or Duplan 2?
Actually, I tried Mastodon,
but then I didn't continue there.
So I sent out a few posts there or two,
but I didn't continue.
I must admit,
I'm on both and I much prefer Twitter.
I just know a lot of people in the dotnet space
that I was following and engaging with on Twitter,
have moved away and now are primarily on Mastodon,
which is kind of a shame,
because as I say, I prefer Twitter.
But yeah, it's kind of like another two places.
Before, Twitter was just a great community,
especially on the dotnet space.
It's a bit of a shame, really.
Twitter is weird right now in many ways.
When you're just using the platform,
you don't even notice it.
You don't notice any big difference.
The media around Twitter is crazy,
especially what the guy is doing there lately.
That's just crazy.
But just using Twitter,
you don't really notice any difference.
Like, I'm still quite used to it.
The other idea we have is,
so we definitely want to have some form of community channel,
whatever it is, might be Discord,
might be Slack.
We didn't really think about that yet.
It's just that we said, hey, we need to have something.
Like, we have an internal Discord server for us,
which is barely configured right now.
That we might turn that into a community thing,
but we didn't really think about anything further.
We do LinkedIn, we do Twitter right now.
It's funny.
I don't know if you read my mind then,
but my next thing I was going to ask was actually about Discord,
because I mentioned earlier that move the podcast
from Slack to Discord,
and DonatOxford,
we've actually just moved from Slack to Discord
and kind of invigorating Discord a bit.
And it does feel like
that would be a perfect thing for we are done at.
Discord is crazily amazing.
I really like Discord,
especially if they ramped up the whole integration aspect,
so you can really get a ton of things into Discord quite easily.
For example, we thought about having a separate channel
for anyone who signed up as a creator.
I mean, that's like four lines of code or something.
Do an API call to us, here you are.
So that's really easy.
Moderating Discord is really easy.
They have a lot of,
they have a thing called AutoMod,
which already is quite good in moderating the channels.
And on top of that,
I mean, even Matthias doesn't fully know that yet, I guess.
The Donat Foundation reach out to us,
because they really, really like what we do.
Basically, they said something like,
oh, we should have come up with that ourselves quite a while ago.
And they really like what we do.
And they have a Discord channel, which is barely used.
We don't have anyone yet.
Nothing is set in stone.
There's no agreements made or anything,
but we are talking to them.
Oh, I'm talking to them about possibilities.
And one thing could be to have a common shared Discord server.
That'd be cool.
Yeah, well, the things I like about Discord is,
well, I think it's luck.
It feels like you're creating an account for everything,
every different thing where Discord,
you've got one account, which you can go to each one.
But they also like the fact that the DMs are outside
each of the different servers.
So it's kind of like, if you want to,
if you want to say DM me on Discord,
it's not talking about a particular server,
it's talking about, yeah.
I think that's one of the top suggested features
for MS Teams since a couple of years,
to be able to easily talk to people on a different tenant.
It works sort of these days.
I think they added that at some point,
but by far, it's similar to what Discord does.
Yeah, I can pitch with MS Teams
because it's quite company-oriented.
It's like for businesses.
Yeah, it's not a community thing, really.
Yeah, exactly.
But yeah, that's cool.
The.NET Foundation,
they didn't realise they had a Discord channel,
so I might join that.
There is one, yeah.
There's not much in there, but there is one.
Another thing I saw quite recently on Twitter
is a nice image with a whole bunch of swag,
saying we are.NET, like t-shirts, stickers,
or a hoodie or something.
That tweet was crazy.
I didn't expect anything similar to it.
Like, really, no.
Well, I was playing around with Spreadshirt,
a company where you can design, work,
and, well, they do all the full women for you.
So you only design the stuff and set a price,
and they do everything, shipping worldwide, stuff like that.
And I ordered a batch,
like you can see where that nice hat here.
Well, people in the podcast can't see,
but yeah, I have a nice hat.
I just ordered a couple of things, like to test it.
And I was like, wow, that looks really cool
when I had it in my hand.
I was like, let's put that in a tweet.
And within minutes,
so there were tons of likes on that
and tons of comments.
And I think that tweet alone got us from 880
to more than 1000 followers, no?
Oh, wow.
I did not expect that,
but I got a couple of messages on Twitter.
We got tons of comments that people like the design,
like the thread and whatever.
So we really need to figure out how we can get that to people.
Oh, very nice.
Yeah, I've got onto here, I've got a .NET shirt,
but it's not We Are .NET, so I'm gonna have to get them out.
That's a developer thing.
I mean, people like that,
and there's a ton of people who like
that they are part of the Donat community.
I mean, that's what actually makes the thing so good,
that I've seen that in other developer communities as well,
like the Java community is quite strong,
or the Angular community, for example.
They are really, really strong.
But the .NET community is great.
Like, especially if you are an MVP,
if you're in the MVP group,
sometimes you can see that people really laugh .NET.
They laugh to tell everyone they are using .NET.
They laugh to wear sweat,
that somehow says, hey, I work with .NET,
and that's really great.
Very cool.
So if one of the listeners is a creator,
but they are not on We Are .NET,
what process would they go through to get on it?
I know I've seen things like with PR requests with JSON
for these card things.
Can you explain how that works?
Do you want to take that?
Yeah.
So it's actually two steps.
So it means you can just sign up with GitHub on VR.NET.
Go to the site, click Sign Up, fill out the form.
So then we have your account basically with your GitHub handle.
Then you can make a PR request with a JSON car.
So you see tons of examples.
All the other creators, also an example JSON,
where you can fill in the details.
And then we run the creative verification process
from time to time.
And then you're all set.
So you would have your feeds,
which can be in two categories.
One is personal.
So there we allow content that can be a bit off topic.
And then we have the .NET category,
which means that it should be about .NET directly or indirectly.
And that's how we keep the feeds clean on the landing page
and in the content area.
But I think as a creator,
you just can go to the homepage, sign up,
and then it should be easy to get from there.
And of course, if you have any problems,
you can always reach out to Tim or me on Twitter or LinkedIn.
Tim.
The whole idea we had was that GitHub-based approach
is that we wanted to have some form of,
I mean, gatekeeping is probably the wrong word,
but we wanted to have some verification process
to make sure that the feeds people sent us
are actually good enough in terms of
not necessarily the quality, what they sent in.
We don't look at every video.
We don't read every single blog post
because that's literally impossible.
Right now we have like, I think,
3.2K, something in the database.
We can't look at all that.
That's literally impossible.
But we want to make sure that people send us feeds
that actually contain content which relates to us.
So if you talk about .NET hosting on Azure,
maybe digital studio extensions or anything
that sort of belong to the ecosystem,
that's completely fine.
We had some creators which are still on the platform
that totally fine, but who are more talking about social things,
being a great leader, stuff like that,
which is important as well.
It sort of relates to .NET as well,
but we don't want to have that on the landing page.
So they can have these kind of things
on their profile page.
That's why we separate the .NET feed
and the personal feed.
So whenever you want to have more than .NET content,
you can give us two feeds,
one filtered for .NET content
and the other with whatever you're talking about.
That's really nice.
I'm actually just looking at my profile on the We are .NET
just so I can kind of like give,
because obviously it's an audio-only podcast
to try and give the listeners an idea of what it looks like.
So it's literally we are .NET.IO slash then my username, Dracan.
And it looks really, really good.
I've got to give my hats off.
It shows a feed of my YouTube stuff.
So it's got all the thumbnail stuff of each video.
It's got links to my social stuff like Twitter, GitHub, LinkedIn.
No master don't, no master.
I don't know that might be my fault for not adding it.
And what we've got.
And there's the links, a feed and the links.
Which takes, oh, is this, so it's the links one like,
oh, is this just repeating my links
when I go to the links tab?
Yes.
Yeah, that's it sort of,
well, it's a little bit work in progress.
The normal members,
which are not creators,
only had a page that shows their links.
And I said, that's not nice.
And tell the normal people also have the nice about section
on the left hand side.
And they also have links now.
And yeah, we're working on the design really.
That's why we still say it's a beta.
We're not completely happy with it.
I mean, the whole thing didn't exist like a month ago.
We're still working on it and still improving everything constantly.
So things are changing a little bit.
Yeah, it's crazy speed.
As you say, if it didn't exist a month ago
and all that's happening now, that's very impressive.
And when you say it's not finished,
I don't think software isn't finished, is it?
It never is.
Yeah, that's true, definitely.
The idea we had for the weird.net platform
obviously started from the.net creators.
So everything Matias did over,
I think over a year, roughly,
is what he was working on.
And that sort of was the groundstone for the whole portal.
But I always thought that the creators
are a huge part of the net
and a huge part of the net education, for example.
That they help people get started with the net.
They help people learn and improve their skills.
Like even I had a video the other day of some creator.
I really, really liked that really helped.
But we said, well, the whole community is more than just videos and blog posts.
Obviously, there's a ton of people with great projects
who work on open source solutions
that really, really help.
And these deserve some form of platform as well.
Many of these don't produce any blog posts.
I was talking to Matias a while ago
and we realized there's two kinds of people.
There's people creating content
and they might have a GitHub repository
just to produce some samples for the blog posts or videos.
And then there's people who run a full blown open source project,
some library, some full blown application, whatever it is.
And they just occasionally write a blog post
or do a video about their work,
which is a completely different thing sort of.
And we said, hey, we actually need to support both types.
So we actually need to add open source projects
on the platform as well.
That's a very, very good point, actually.
I must admit, I hadn't really thought about it that way.
But yeah, so many people
putting so much of their free time into these projects.
And if it's an existing project,
you probably, if someone does a blog post
and tweets out about it,
then it gets various retweets,
so I tell them because it's a new announcement,
a new thing being created.
Where if it's a project that's already existing
and everyone's using it because it's in lots of value
and it's being maintained,
a lot of work still goes into that.
But it probably gets less of a platform ongoingly.
I know that's one thing that Nick Chapzass in his videos,
he quite often really tries to pick out
these open source projects and really promote them.
And things like in the podcast as well,
Simon Krupp's been on before
and he's done his verify library.
And I know that's when you were talking about
open source maintainers,
he jumped out of my mind
because he does a ton of stuff on his library.
And you can't even mention a technology
and then who had an extension
to support that in his verify library.
And it's like, he does quite a lot.
And I was looking at,
in fact coincidentally enough yesterday,
I was, there's a serilogue sync for open telemetry
where it's actually not really been touched that much.
But it's something I would find quite useful
for something I'm doing.
And I looked at it and Simon was on it doing commits in there.
So it's like, whoa, he's everywhere.
But yeah, these maintainers, as you say,
that don't blog or don't create YouTube videos and stuff,
they need to have a platform too,
some way of marketing that stuff in a way.
Yeah.
And the other thing is,
I have a hard for open source in many ways.
The one thing that always makes me mad,
sort of, is to see how some of them are struggling.
Like, I'm not sure if you remember the thing
that happened with the identity server, for example.
They said, after all,
they earn like 50 grand or something per year from donations.
They did that as a full-time job.
And I think identity server four was used
in probably a million applications.
I don't know.
That's one of the most used thing
in the whole.net ecosystem, I guess.
And they literally didn't get any,
well, not the proper funding or feedback they deserved.
And they said, okay, we stopped doing that open source.
We are actually making that a paid product now.
We're just completely un essential.
And many, many companies in the open source field
need a lot more attention.
If I had way more money,
then I would probably go out there on GitHub
and donate quite a few of these.
Well, I don't, I can't, but with We are the Net,
we can at least give them a platform
and try to get them more attention.
Yeah, definitely.
That'll be very, very good to see.
So talk about open source and stuff.
I'm assuming that all the stuff we're talking about
with We are the Net,
like the website, the mobile app and everything,
is that open source on GitHub as well?
Not yet.
I thought we want to have a pretty good structure.
I have, well, it's constantly changing right now.
I move things around.
I move, well, it's based on.net core.
I move controllers around.
Just the other day,
I moved all things in a separate model class
just to have it more structured.
I think it's five services now.
So it's rapidly growing.
And at that point,
it's hard to take in any contributors or anything
because having to explain all that to someone,
it's just, it just doesn't work.
So I want to have that up to a point where we said,
okay, this is actually not beta.
That's a final product now.
We're happy with what we have right now.
And at that point,
I actually want to make everything open source
and people can contribute as well.
Très nice, très nice.
Is there any other areas that we've not covered?
Yeah, I do have one thing I would like to talk about.
We have one thing we are unsure about,
which is a little bit about how we deal with things like
Spondort ads, companies asking,
hey, can you put our job at there or whatever?
So we always said the whole platform is free,
will always be free.
It's open source, whatever.
But obviously with a platform like that,
there is quite a lot of builds
because it all runs on Azure.
We use Azure cognitive search
and quite a few other services which have to be paid.
So we need to find some way,
not right now, right now it's still fine,
but depending on the growth at some point,
we need to find some way to get all the things funded.
We always said,
we don't want to turn that into a job portal
that will never happen.
So we won't, we'll never have like,
oh, use like dotnet jobs or whatever.
There's tons of platforms for that.
I don't want to do that.
We might ask companies
whether they want to sponsor us or something.
The dotnet foundation probably might help here as well.
I don't know.
But I think it's important to say that we never,
we don't want to do any profit with that.
So I think that Matthias, for you,
that was really important.
You mentioned that a couple of times as well.
We don't want to earn money with that.
We even said if we get funding
and if we ever have more money funding-wise
than we need to pay our bills,
we would give back the rest to other open source projects,
donate that,
or buy a bunch of t-shirts
and hand them out to the community, stuff like that.
I don't know.
So if we, at the end of money,
there's a zero, that's completely fine.
That's all we ever want.
And I think that's important to mention as well.
Yeah, it makes sense.
Cause it's kind of like, you kind of think,
it's easy to forget that
even though it's kind of a non-profit thing,
things like hosting and things don't actually cost money.
So it's got to come from somewhere.
It's like, with a podcast,
I'm not earning anything through doing the podcast,
but I've had to buy a lot of equipment.
There's the podcast hosting sites.
I use Buzzsprout.
There's what we're using now, Riverside.
So each of these has a subscription.
So there's, even though it's not a profit,
there's still costs associated with things.
So I kind of wonder whether,
when you do actually do your GitHub thing
and you make things open source,
when it's in a position to do so,
I know GitHub has that sponsorship thing.
So maybe that's a possibility.
Yeah, they do.
I mean, even I'm an MVP.
So MVPs get a little bit of Azure grant every year.
So it's sort of based on that right now.
But there's other things we have to pay,
which are not as easy to get by.
So we're using pre-renda IO,
which is taking care of search engine optimization,
which is helping with the link preview,
the link un-throlling that helps.
And it's a really, really great service.
I wouldn't want to miss that.
But that's not part of Microsoft or GitHub or whatever.
So we have to pay them anyway.
The whole pages,
or most of the pages hosted on Cloudflare,
we even quite a few Cloudflare services,
especially to improve performance and all that.
That also has to be paid for separately
because they are not related with GitHub or Microsoft.
Based on the Azure hosting fees,
I'm pretty sure there's tons of ways
we don't have to pay that
because Microsoft has a pretty, pretty good community offering,
even like GitHub as well.
And so I'm pretty sure we can sort that,
but that's by far all of it.
Yeah, yeah.
I don't have interest with the Cloudflare one
because I use it for quite a lot of my sites,
but it's the free-to.
What is it that requires the paid for?
Well, we use Cloudflare pages just for the,
well, the pages based on QJS.
So it's a view three application.
We use Cloudflare pages to host the front-end.
We also use Cloudflare pages sort of as our CDN,
our whole media repository for all the images
and all that is on Cloudflare as well.
And also Cloudflare has a worker
which redirects any bot traffic to pre-render.
So any traffic coming from Googlebots,
Twitterbot, whatever goes to pre-render IO
to get a pre-rendered version
because the dynamic view version
just doesn't work properly.
And you have to pay for the worker hours.
I think it's in the free version.
I think it's something around 100,000 per year,
per month or something.
Right now, we are at 12,000,
so that's completely fine.
So nothing to worry about.
But at some point, depending on rows,
depending on visitors on the website,
that quickly sums up really.
Yeah, I forget that Cloudflare does hosting
and all a whole bunch of other stuff.
I just use it for CDN.
So you get quite a lot for free,
but then if you're using it for hosting,
you're all done.
That makes...
Right now, it's not an issue at all.
Like most of the stuff we do right now is for free
because we are still in a size
where the free tiers just work fine.
We use odd 0 for authentication, for example.
That's good up to 7,500 users per month.
So we're still far away from that.
So no problem with that.
But at some point, depending on the rows
and depending how things continue,
we might actually get problems regarding these things.
Yeah, especially with all 0
because that gets...
When you get the paid for one,
that becomes suddenly very expensive.
Yes.
Yeah, it's funny in many ways
that I realized again,
building such a thing like a community page
is not too far away from building
a full blown software as a service thing.
We use the same things.
We have a.NET Core back end.
We have Redis.
We have Azure Search for that.
We have an SQL database
where all the things,
a normal application would use as well.
Yeah, definitely.
It always surprises me
when I go back and do
that old.NET Framework development
or something like that.
And then you realize, actually,
how far.NET has come now.
Well, actually,
a lot of the things you said then,
it's obviously complicated.
But once you know it,
you can actually knock things up quite quickly.
I was working for teamwork.com,
a project management platform
four years ago, five years ago.
And they chose to use
Golang as their main back end thing now.
And a lot of that is because
they had really, really bad memories of.NET.
They were trying to do something
with ASP forms back in the days,
which obviously was really, really bad.
Like, don't have to make that a secret.
It was really, really bad.
But Microsoft came a long way
since then and things really, really improved,
especially with the later.NET Core version.
Things are really, really great
and competitive as well.
But it took a long way.

A recent talk
as a local user group in Oxford
about modern.NET development.
Because the basic, the crowd were developers,
but not many.NET developers.
So it's kind of trying to raise awareness.
And as I was talking to this,
one of the sections I had was about performance.
And I mentioned a blog post by Steven Taub.
I think that's how he pronounces his name.
And he always, every year,
for.NET, every new version,
he writes a massive blog post
about all the performance improvements
that have gone into that version.
And bear in mind that they do them yearly now.
And in the slide, I did like an animated GIF
of me scrolling down his blog post
and scrolling, and scrolling, and scrolling.
And it's insane all the work
that goes into the performance.
And this is each version.
It's just so fast now.
Yeah, it's funny.
I want to mention that it's funny how
the page just helped me already myself.
Like, I had something,
I wanted to use views and start procedures
in Android framework.
Because Azure Search works a lot better
with the view and just the pure table.
Because I want to have more than just a single table index.
And I remember that one creator
actually had a video about that.
So I just looked it up on the page,
watched it again, and that really helped.
So I actually used my own search functionality
already to help me.
So I think that's a good proof.
Oh, very nice.
It's always good when you can dog food your own project.
Yeah, yeah.
I actually like the,
I'm not sure where the term is coming from,
but I actually like the dog food term.
I mean, some people name it,
eat your own dog.
I'm not sure if I'm allowed to say that.
But I think that's really, really important.
Because if you can use whatever you build,
then probably there's other people.
And if you hate what you build,
then probably other people hate it as well.
Yeah, as a developer,
you're not working on your own thing.
You don't think about the user flow
and you think about the technologies
and the architecture and everything.
Yep.
And then, yep.
If you watch over the shoulder of someone
that uses it, it's like, oh,
you do it that way, then.
So that's kind of, kind of,
can be quite eye-opening.
But if you use it yourself, that's even better.
We actually had that a couple of times.
Matthias is a lot using the mobile phone.
So he's a lot looking at weird on it on his phone.
While I'm mostly looking at it
on my normal Chrome instance
and even on a 4K screen quite often.
So I missed a couple of things
he saw instantly on his phone,
which I didn't even see
because I missed testing it on my phone.
So, yeah.
I think the problem with the end users as well
is, kind of, quite often,
if there's something that's not quite right
and there are more clicks than it needs to be
or whatever it is,
then most of the time, they won't tell you.
They'll just work around it or something.
So actually, doing it yourself,
you're catching things that maybe other people might
have been annoyance to other people,
but not actually.
They might not raise it to you.
It's even worse.
Like, I've been in,
I've heard people say,
hey, this is not working well.
I don't like that product, whatever,
just because of a small bug, really,
because of something
that was never meant to work like it did.
And they did not complain or ask about that.
And instead, they just say,
oh, no, I don't like that and move on.
So, yeah.
I think that's a majority of people, actually.
Yeah, definitely, definitely.
So, looking at the time,
we should probably get onto dev tips.
Was there anything else you wanted to mention
about WeR.net before we even moved to dev tips?
No, I don't know.
No.
Cool.
So, let's do dev tips.
One dev tip I would have,
it's like never stop learning,
just in general.
And the one thing I like is Got Handleman
had that a while ago
in one of his TikTok things,
I think I can't get the full words,
but he said something like,
at the end of the year,
do you want to be the one who read a ton of books,
who attended a ton of conferences
and who looked at a ton of samples
or do you want to be the one
who actually wrote the books,
who gave the talks
and who actually published all the samples?
So, you have all these knowledge,
like a ton of developers
have a ton of knowledge in their head.
What do you do with that?
If I tell someone,
I was an engineer manager for quite a while,
like right now I'm not,
and I'm sort of happy that I'm not
because I can just work for myself.
I like being an engineer manager,
but at some point,
you are happy if you're not responsible for people,
like for a while at least,
because it can be quite exhausting
and at some point you're happy about that.
However,
you can work on something
with all your experience for yourself,
like you take eight hours,
you build some piece of code,
whatever, you write some code,
or you can tell others
how to actually write that code
and have them build it
and that actually multiplies your knowledge.
And these people can then go ahead
and write the same thing
and like you can tell that to 10 people
and then 10 people can do what you can do.
So actually, A, learning
and B, sharing your experiences.
I think one of the most important things
in for every developer,
really not even readatetut.net.
Yeah, definitely, definitely.
I always think about it as like you're learning,
you're learning it more than twice
because if you're going to do a talk
or you're going to teach someone,
you generally remind yourself about it before.
So you've initially learned it,
then you're reminding yourself.
Then when you're talking through it
and articulating it, you're learning it again.
So by sharing your knowledge,
you're learning it two or three times
what you would have done without doing it.
Mathieu, did you have a dev tip?
Je voudrais vous ajouter,
je vous recommande vraiment
d'avoir un blog,
même si vous êtes juste au début de votre tour de.net
parce que ça vous aide à comprendre
ce que vous connaissez déjà dans un nouveau moyen.
Et puis vous pouvez vous improvement,
vous avez beaucoup de feedback
et avec des choses comme social media
et bien sûr, sur votre.net,
vous pouvez savoir d'autres créateurs
et avoir des feedbacks de eux.
Et si vous n'êtes pas sûrs de commencer tout ça,
vous pouvez, par exemple,
aussi joindre le groupe de LinkedIn privé,
vous demandez vos questions.
Certaines personnes parlent
sur quel blog système ils doivent utiliser.
Donc ça peut être solué.
C'est vrai, peut-être que je peux le dire?
Quelqu'un m'a mentionné un peu d'an ago
que si vous ne savez pas ce qu'il y a à faire
comme développeur, vous pouvez commencer à faire ça
comme un délirement, vraiment.
Hey, aujourd'hui, je fixe ces problèmes.
Même ça peut parfois aider.
Et surtout, ce qui m'a aidé aussi
est le stack overflow.
Je pense que le stack overflow
est complètement narré.
Juste l'autre jour, je me suis regardé
pour quelque chose, j'ai trouvé une solution,
j'ai écrit l'answer moi-même,
comme 10 ans plus tard.
C'est ce qui s'est passé.
Et j'ai entendu beaucoup de gens
dire exactement ça.
Oui, juste l'autre jour,
j'ai trouvé ma seule solution
pour être aidé.
Le stack overflow est vraiment grand.
Et juste par la question
d'autres personnes,
vous pouvez être capable de l'answer.
C'est vraiment un bon moyen
d'en commencer.
Donc, avec blogging,
vous inquiétez que,
par exemple,
à la fois avec chat GBT,
par exemple,
vous pouvez l'asquer
pour faire un blog poste
en ligne,
faire un blog poste en X.
Et ça fait
une grande chose,
vous ne savez pas
que c'est écrit par un bouton second.
Je me demande
ce que ça va faire
pour blogging,
mais pas juste blogging,
parce que je ne sais pas
si vous avez entendu la tour de la course
qui est l'article AI.
Et c'est absolument incroyable.
Donc,
toutes ces choses,
vous inquiétez
ce que vous allez faire
pour les humains
qui en faisent ces choses.
Je n'ai pas un
pas complètement,
mais un sens opposé
parce que,
oui,
ça peut produire
vraiment bon contenu,
mais c'est aussi
bien d'accord
à la même fois.
Quoi que ce soit,
c'est vraiment mal.
Parce que
ça ne sait pas
ce que c'était pour le train.
C'est tout ça.
Si vous pensez à Github Co-Pilot,
par exemple,
c'est un peu similaire.
C'est
un excellent
saison.
Ça me permet vraiment
beaucoup de

Vous pouvez faire des choses
plus vite.
Et je vois
une chute GPD
de manière similaire.
Ça peut
vous aider
à commencer à l'étranger.
Comme,
ça peut
vous donner
des outils.
Ça produira un blog
pour vous,
qui est 80%
fine.
Et vous êtes encore
à des
tweaks
et vous le faites bien.
Et c'est
ce qui est vraiment,
c'est vraiment,
vraiment,
aidant.
Comme,
faire le premier drap,
en prenant des choses
pour vous,
en faisant
comme,
la plupart des choses,
vous avez des aigus bandés.
Ça vous permet
d'avoir un start-up
dans les choses.
Donc,
ça vous permet d'avoir
plus de temps
pour les choses importantes.
Mais ça ne va pas
répliquer
quelqu'un
dans cet sens.
Je suis un peu
agréable
maintenant.
Mais,
si vous me montrez
une chute GPD
un an plus tard,
ce que c'est en train de faire,
mais la main
est encore brûlée.
Je ne peux pas
croire
que ça va faire
ce que c'est en train de faire.
Donc,
et ça va
se faire
faire le start-up,

Donc,
en 5 ans,
c'est
toutes les choses
que vous avez mentionnées.
Est-ce qu'ils vont
encore être
un problème?
Est-ce que ça va
être correct
tout le temps?
Et c'est comme,
je pense que c'est comme,
comme,
on est en train de
faire l'un des plus grands
changements
que nous avons
vu
depuis un très long temps,
depuis le computeur.
Je pense que
ça va changer
un ton de travail.
Ça va changer
un ton de choses
dans l'industrie,
en général.
Il y a même
services qui peuvent
produire une vidéo.
Je veux dire,
il y a Stalie
produisant des images.
Et juste l'autre jour,
j'ai vu
des...
Je ne m'en souviens pas
de l'un ou l'autre.
C'est produire des vidéos.
Donc,
vous vous donnez une promesse
et ça vous donne
une animation de gif
ou quelque chose
qui est générée
à base sur votre promesse.
Et,
oui,
il y a tout le discussion
avec les spots.
Et si l'A.I. est dangereux,
tout le
lost food,
tout le
top-C,
C.E.O.C.E.O.
ou quelque chose.
Je vais dire,
hey,
s'il vous plaît,
je vais dire,










je vais dire,
je vais dire,

je vais dire,


je vais dire,



















je vais dire,
















je vais dire,






je vais dire,


je vais dire,








je vais dire,
et il a déjà appris
des nouveaux jobs,
techniquement,
parce qu'il y a,
comme le jour d'autre,
je l'avais regardé
quelque chose,
il y avait une compagnie
qui demandait
pour des ingénieurs prompt.
Il y avait une compagnie
qui achète
des ingénieurs prompt
de l'I.I.I.
qui était le travail
qui n'existait pas
un peu de mois plus tard.
Donc, il nous a même
appris des nouveaux jobs.
Et on a,
juste le jour d'autre,
on a eu une discussion
avec l'interne
dans DeepEle.
Donc, DeepEle
fait des machines
et des transactions

C'est pourquoi la qualité
est si bonne.
La qualité que nous avons
est en fait
beaucoup plus belle
que Google ou Microsoft.
Mais
ce n'est pas parfait.
Donc,
je pense que quelqu'un
m'a dit,
hey,
si vous vous translate
un document légal,
nous devons être
à 95%
et le reste
il faut le faire manuellement.
Et ensuite,
nous parlons de
ce qu'il y a besoin
pour s'y arriver à 100%.
Et nous avons dit,
c'est pas possible.
Nous ne serons jamais
un 100%
accuré de la transition.
Juste parce qu'il y a
tellement de choses,
il y a des bruits,
il y a beaucoup de choses,
il ne peut pas
faire automatiquement.
Je veux dire,
nous devons être
assez proches,
à 98%,
à 99%,
peut-être.
Mais vous ne verrez jamais
100%.
Et je pense que c'est le même point
pour des choses
comme l'Agence de l'Etat.
Oui, c'est bon,
c'est bien,
il y a déjà
des documents
générés par l'Agence de l'Etat
qui,
même
les docteurs,
les ingénieurs,
n'ont pas pu
identifier
comme l'Agence de l'Etat.
Oui,
mais nous ne serons pas
à 100%
à dire que tout ce qui
s'est fait de l'échec de l'échec de l'échec de l'échec
est parfait.
Je ne pense pas que nous ne verrons jamais.
Oh, c'est bien.
Je dirais que jamais,
jamais, mais...
Oui.
Oui.
Donc,
en parlant de l'AI,
ce qui était sur le plan,
mais qui a léglise
bien dans mon dévité,
je me garde à
faire ce qu'il y a avec Linkpad,
et on a
eu un épisode sur Linkpad
avec l'Auther.
Et je n'ai pas fait
des vidéos sur Linkpad,
qui est,
pour des raisons,
je ne sais pas pourquoi,
il se fait
un peu de trafic
et je ne sais pas pourquoi.
Mais je le vois
dans la version la plus lente
de Linkpad.
Il y a un AI,
l'AI Linkpad,
qui s'entend à
le chat de l'AIS,
l'AIS OpenAPI.

c'est un peu,
ça vous donne
tout ce
chose,
mais en ligne,
je pense que si vous pressiez le shift,
vous avez un
complet auto,
donc vous pouvez mettre un comment
avec ce que vous faites,
et le shift
et ça va
mettre
les résultats,
comme l'AIS Open.
Et il y a un whole bunch
de refacturations
que vous pouvez dire,
pour faire les tests de l'AIS,
pour votre code,
et c'est tout
dans l'AIS,
ce qui est génial.
Donc je vais en faire
mon prochain vidéo YouTube,
je vais créer
ce que je vais faire
sur ça,
ce qui ne l'a pas été fait
en temps de la recording,
mais en temps
que ce épisode de podcast
se passe,
ça probablement
sera publié
si je l'ai créé,
si je n'ai pas encore
fait la recording,
mais
oui,
je vais faire
un lien sur ce show,
c'est juste
l'AIS,
tout le monde,
c'est
assez
incroyable.
Oui,
je pense que
vous avez accès
à quelques choses,
que les autres ne l'ont pas encore.
On a un invité
à ce nouveau,
ce que l'on appelle
Github,
copilot,
Chat,
dans le studio.
C'est un pire incroyable
de technologie,
c'est vraiment
incroyable.
L'AIS
est juste
tout le monde,
je ne suis pas sûr
si vous avez vu
l'annonce
pour le tout
Microsoft 365,
copilot.
J'ai vu
seulement un couple de vidéos,
mais
comme
construire un présent
par juste écrire
un couple de
lignes de textes,
et ça vous donne
une whole présentation
avec des animations
et tout.
Oui, c'est bien.
Je ne sais pas si vous avez vu ça.
Donc,
oui,
c'est
et puis
c'est
le stuff de
copilot,
qui
j'ai vu
une vidéo
récente
sur YouTube
de Nick Japs.
Il n'a pas encore
mais il était
en train de
l'annoncement
sur
tout le futur.
Et à l'end,
il était en train de

si quelqu'un
de Microsoft
est en train de

s'il vous plait,
s'il vous plait,
donnez-le l'accès.
Je ne pense pas
qu'il a un point
peut-être qu'il a un point

je ne sais pas,
mais
on peut
on peut tout le book bag.
Oui,
je vais faire le même
comme lui,
si quelqu'un
de l'est,
s'il vous plait,
donnez-le l'accès.
Je n'ai pas l'accès à ça.
Je ne suis pas trop
capable de le dire,
mais je n'ai pas l'accès à ça.
Et c'est,
c'est bien.
C'est copilot X,
le même chat.
C'est le même
que
copilot,
mais basé sur
le GPD4.
Ah,
OK,

Et je pense qu'ils ont
fait un couple
de plus
d'éditions.
Je ne sais pas.
C'est beaucoup plus
plus
basé sur le GPD4.
Il y a aussi,
je ne pense pas
que ça soit
lié à X.
Il y a une extension
que vous pouvez installer
en code VS,
comme
copilot Github.
Je ne sais pas
ce que l'on appelle.
Et ça vous donne
quelques choses.
Il y a un bouton
de reforme,
mon code,
un bouton de
faire mon code robuste.
Et ça
automatiquement
attirera et attirera
tout le monde,
tout comme ça.
C'est très important
pour les
les codes link.
Ils ont été regardés.
C'est très cool.
Et même les choses.
Je vois
toutes les applications
que vous utilisez.
Je utilise la notion
assez grave
pour les notes.
Et ça a un AI
maintenant.
Donc,
si vous commencez
à la notion
d'espace,
ça commence
à tenter de prédiquer
tout pour vous,
ce qui
est à l'aise.
Et ça a un AI.
Donc,
je pense que
tous ces compétences
sont en train de
mettre sur l'AI.
Cool.
Donc,
je regarde le temps.
Donc,
ça devrait être
pas mal.
Mais avant
nous finissons,
où est le meilleur
endroit pour
les listeners
pour atteindre
pour trouver plus
de Mononord.
Si
vous plaguez,
si vous avez des questions.
Cela se points à
la photo d'Édone
whereas illegally
comme le tout
plus
ascénuestre.
On akrä Daten
je ne représente pas mes photos, mais je me souviens de buckle, je France, j'ai fait ma
donc les listeners peuvent vous trouver de cette façon.
C'est cool.
Merci beaucoup d'avoir regardé ce show.
C'est un très cool talk about WeAre.net,
et j'ai hâte de voir où ça va,
car comme je le dis, c'est un peu grand,
c'est très impressionnant.
Merci beaucoup d'avoir regardé.
Je voulais vous dire une chose,
je pense aussi à l'adresse des podcasts,
parce que James a demandé ça,
parce qu'il a aimé entendre les podcasts,
et donc on peut avoir un podcast sur We Are.net,
ce n'est pas trop grand,
on n'a pas de créateurs et de vies,
mais on va probablement avoir une liste de podcasts de We Are.net.
J'espère que ce podcast va être un bon podcast,
et que ça va être sur la liste.
Ça dépend de votre skill de la production.
Je vais le voir.
C'est probablement un peu de choses,
j'aime vraiment votre podcast.
Merci beaucoup.
Merci d'avoir regardé,
et je remercie de vous rapporter de ce podcast sponsorisé par Everstack,
qui est mon propre company,
qui donne des services de développement et de consultation,
pour plus d'informations visites à Everstack.com.
Si vous aimez le podcast,
s'il vous plait,
vous pouvez me séparer sur le nom de la social,
je sais que je n'ai pas utilisé le hashtag
et je peux être foundé sur Twitter,
sur Jack Han et mes DMS.
On a évidemment le canal Discord,
et les DMS sont aussi là,
donc vous pouvez me le donner.
Je suis sur un blog,
www.banklock.com,
il y a des liens à tout mon stuff.
Je vous remercie de vous rapporter de ce podcast,
et nous allons inclure les liens à toutes les choses
que nous avons mentionnées aujourd'hui
dans les notes de la show,
qui peuvent être trouvées sur www.unhandledexception.com.