Leave a comment below to introduce yourself! You can talk about what brought you here, what you're learning, or just a fun fact about
yourself.Reply to someone's comment, either with a question or just a hello. π
Come back next week to greet our new members so you can one day earn our Warm Welcome Badge

Top comments (526)
Decided not to continuously copy/pasting the same message over and over again and decide to be genuine again.
With that said, Welcome everyone! What brings you here?
hii
hey
hiii
Hi Francis , Just found my way here and figured Iβd join the community. Hoping to learn a lot and maybe make some cool stuff along the way ππ and Iβve been learning and building on my own, and thought itβd be nice to actually connect with other developers doing the same.
That's cool - You will be always having the latest updates too.
β€οΈ
Welcome, Manal! Python is a great first language, and it's also really useful for automating everyday admin tasks. Enjoy the experimenting phase; that is where most of the learning happens.
Thank you Priya ππΈ
Same here! Hope you will find your place here on DEV! What things have you built so far that your proud of?
Well Iβm pretty new to coding actually , Iβve just started learning Python. So far Iβm focusing on the basics and experimenting with small things. Excited to see where it takes me ππ
Welcome! π
Hey Francis! Brought here by a failed backtest, honestly. I've been running quant experiments on crypto and prediction markets, and realized the only way to make it useful is to write it up publicly. Just posted my first article β Sharpe 13.4 before trading costs, -40.1 after. Clean failure, but worth documenting.
Welcome, Pavel! Writing up the failure is the right call; far more people learn from those than from the wins. A Sharpe of 13.4 before costs is a useful flag in itself: numbers that high usually mean the strategy trades so often that costs are most of the story, or something in the data is too good to be true. How many trades a day was it making? I'd love to read the write-up.
Thanks! Yeah, 15-minute rebalancing across ~20 coins β easily 200-300 position changes per day. Turnover killed it before anything else got a chance.
Already moved on to other hypotheses, like funding carry, momentum, and a football prediction model. All failed for completely different reasons. Writing them up as I go.
200 to 300 changes a day explains it: even a few basis points per change adds up to more than most signals can earn. Writing each failure up also sets you up for the part people usually skip, which is that every hypothesis you try adds to the count. If funding carry or momentum eventually passes, the fair bar for it is set by all the ideas you tried before it, not just its own backtest. Your football audit post is next on my reading list; five checks is more than most people ever run.
That multiple testing point is real and I don't have a clean answer for it yet. Pre-registering helped on the football one but across ten experiments it adds up.
And yeah, if you ever have ideas you want stress-tested - throw them my way, I'll run them through and post the results whatever they are.
Heyyy!! this sounds super interesting, would love to connect with you and learn more about your experiments!
Hello!
hellloooo what do you do?
helloo what do you doo??
I am an ai/ml and gen ai enthusiast...currently aiming to ace challenges on this platform
Mostly to share what I learn from working with small teams on Microsoft 365 and Azure, and to pick up ideas from people building in areas I know less about. Nice approach on skipping the copy-paste, welcome, by the way.
Hello Francis
Thank you!
I've seen alot of great posts and i'm glad to feel at home!
Hi! Glad to be hear to learn more about AI/Software architecture, best practices, and cutting edge thought models. Look forward to learning from all of you!
hey bryant, welcome!
Hello! Just wanted to join a cool community of people that's specific to software dev!
I find this site via chatgpt
hi
hello
Thanks for the welcome! π I came here to share the story of rebuilding a 28-year-old IRC community from scratch β Go, WebAssembly and a lot of late nights. First post coming soon!
hello
hi
hi
Hi :)
βοΈ
I just want to share my things that I have built and get to know how fellow devs do in their life.
Hiya
Hey!
hello
Hi there π
Hiiiiii, Major League Hacking brought me here and now I'm hear to stayy
Heyy, new to my dev journey and wants to know more
Hii :D
If your LLM app ever died in production after a perfect demo, say hi :)
Hello from Houston. π
Naveen. Software architect, about seventeen years in, most of it building .NET and Python systems for government agencies. That work means a lot of forms, workflows and business rules that arrive from statute rather than from anyone's product roadmap, which has shaped how I think about software more than I expected it to.
Lately it has been Azure, RAG and ML.NET. The recurring lesson is that the model is never the hard part. Deciding what the system should refuse to do is the hard part.
Read here for a long time, finally made an account. Working on a first post about form builders and validation rules that are themselves invalid, which turns out to be more interesting than it sounds.
@io64bit opening the thread with a hello world is a choice, and I respect it.
Hello Naveen,
I am new here; let's build a good trust.
Welcome to the community! Looking forward to seeing what you post.
Welcome to the party @naveen_alavilli !
heyyy Naveen , 17 years in software is WILDDD!!
i'm a self-taught dev, mostly into react/rext.js, node.js bug fixing, and I LOVE hearing how experienced engineers think about software beyond just making things work.
definitely looking forward to reading your post.
Welcome to the community!!
Thanks, Omaima! Self-taught and already fixing Node bugs in production is its own hard-won experience β the "beyond just making things work" part comes from getting burned a few times either way. Welcome, and hope the post's useful.
Hey Naveen! 17 years in software is impressive. π The part about deciding what a system should refuse to do being harder than the model itself really caught my attention. Looking forward to reading your post about form builders and validation rules!
Thanks Roy! Yeah, deciding what a system should flatly refuse to do usually ends up being the harder design problem than the model logic itself. Appreciate you following along.
Hello everyone !!!
hello!
Hi!
Hello and Welcome!
Welcome! π Loved reading your intro. Iβm curious β whatβs one AI tool thatβs actually made it into your daily routine? Iβm always looking for real-world use cases, not just hype.
Thanks for your reply! That's a really good question. I mainly like to think of AI as a tool instead of a know-all. I only use AI for automations, workflows, and loops using N8N. It's a pretty cool tool since it allows you to connect to many different API's and services. It is also easy/free to download and use with Docker Desktop. Check out how to install and use it here: N8N Docker Install
Hello!!
heyy
I say it in javascript:
Hi All!
Hi
hi
Hey everyone. Nice to be part of this amazing community
Welcome to DEV! There is alot to keep you busy here. β¨οΈ And alot of good people!
Hi
hello everyone
Hi Dino or David or both π
Hello
hello everyone
Hi
hay yawl. I am new here, this is one of the only forms that my boss lets me use so pleas keep it funny I could use it!
Be sure to check out @ben for meme Mondays! Plenty of content to sift through, - past meme Mondays. Feel free to contribute to the nonsense!
Some comments may only be visible to logged-in visitors. Sign in to view all comments.