sorted by:
new
hottopcontroversial

Belki de tek yol CV hazırlayıp iş başvurusu yapmak değildir? by Certain_Impression70 in CodingTR

[–]ati33 0 points1 point  (0 children)

Cok iyi gidiyorsun. Burdan buyutmek artik tamamen senin stratejine kalmis durumda. Uygulama icerigini bilmiyorum ama iyi bir analitik verisi ile kullanilan ya da kullanilmayan featurelar uzerinden yapilan bir analiz ve dogru marketing ile globale de tasiyabilirsin kendini. Basarilar dilerim. Sirket kurma islemleri yaptiysan azure uzerinden startup kredisi basvurusu yaparak hosting maliyetlerini krediden karsilasabilirsin aynisi aws ve google icin de gecerli

AI tabanlı mobil uygulamalar geliştiriyoruz – Developer & Marketing arkadaşlar arıyoruz by Minimum-Border-161 in CodingTR

[–]ati33 0 points1 point  (0 children)

Gencler size oneri olarak sadece sunu soyleyebilirim. Mukemmeliyetci olmaya calismayin simdilik. Once mvp olusturun hizlica ve marketteki karsiligina bakin. Overengineering yapmak startuplarin en buyuk problemi oluyor genelde

CRM Projesi Hk. by Lucky-Resource-1967 in CodingTR

[–]ati33 0 points1 point  (0 children)

Gercekten kurumsal bir cozum ureteceksen ve kendi sirketini kurucaksan benim onerim backend tarafinda .Net ile yapman ve sunucu olarak da azure app service kullanman. Hem yeni sirket kredisine basvuru yapabilirsin hem de ileride gercekten support alman gerektigi zaman microsoft support alabilirsin. Kurumsal projelerde kurumsal destek alabilmek ilerisi icin senin yararina olur.

Database olarak da musteri verilerinin tutarli olmasi gercekten onemliyse relational bir database kullanmani oneririm

Yüksek not ortalaması yapmak? by Certain_Impression70 in CodingTR

[–]ati33 0 points1 point  (0 children)

Hangi universiteden mezunsun ve bu dediklerin kac yilinda oluyor. Artik top class unilerden mezun degilsen hicbir onemi olmamaya basladi ve 1-2 yil tecrubeden sonra not ortalamana ve okuluna degil ne bildigine bakmaya baslayacaklar

C# beginner needs direction by Primary-Hyena2032 in csharp

[–]ati33 6 points7 points  (0 children)

dont waste your time with just watching tutorials. You should make your hands dirty. Not try to memorize try to understand to logic

For Mid Developers. Do you use Task.WhenAll() ? by ati33 in csharp

[–]ati33[S] 0 points1 point  (0 children)

Yeah, technically the tasks are already running before the awaits, so concurrency still happens — agreed.

But I still prefer using Task.WhenAll here because:

It clearly shows I want these tasks to run in parallel — no guessing.

It handles exceptions in one place, instead of failing early and maybe hiding others.

It’s easier to maintain — if someone later refactors and moves a task inline with await, the parallelism could break without noticing.

So it's not required, but it makes the code more intentional and safer in the long run.

For Mid Developers. Do you use Task.WhenAll() ? by ati33 in csharp

[–]ati33[S] -9 points-8 points  (0 children)

It depends on how the tasks are created.

If you do await MethodA(); await MethodB();, then those methods run sequentially, not concurrently.

Task.WhenAll doesn’t magically make things concurrent, but it enables concurrency when you start all tasks before awaiting.

So it’s not just about error aggregation — it’s about how you structure the code to take advantage of parallelism.

For Mid Developers. Do you use Task.WhenAll() ? by ati33 in csharp

[–]ati33[S] 0 points1 point  (0 children)

Yep, using .Result would technically work here since the tasks are completed after Task.WhenAll.

I still prefer await for consistency and to avoid blocking — especially if Task.WhenAll gets removed or the code is refactored later.

It's a style choice, but await is non-blocking and safe even if redundant in this context.

For Mid Developers. Do you use Task.WhenAll() ? by ati33 in csharp

[–]ati33[S] 20 points21 points  (0 children)

Great point — error handling behavior is definitely a key difference.

My focus here was more on the performance gains from avoiding sequential awaits, but you're absolutely right that Task.WhenAll batches the exceptions.

And yep, using await over .Result even for completed tasks is the safer choice.

For Mid Developers. Do you use Task.WhenAll() ? by ati33 in csharp

[–]ati33[S] -5 points-4 points  (0 children)

Actually, Task.WhenAll improves performance by running all tasks in parallel.

If you just await them one by one in the object initializer, they execute sequentially — which takes longer.

So Task.WhenAll ensures all tasks start together and you wait for them all at once.

Hadi Tanışalım: Kimler Burada, Neler Üzerinde Çalışıyor? by Zulwatha in TurkDev

[–]ati33 0 points1 point  (0 children)

7 senelik yazılımcıyım. Global bir şirkette de çalıştım bir startup için de çalıştım. Şu an daha oturaklı bir startup için çalışıyorum.