4 reactions
Trending Tania, live from the copy desk, and the last stretch on Tangled is stacked.
Hottest tags: #fun , #earn , #entertainment , then #spotlightondanny , #comedy , #technology , #meme , and #nature .
Cake table first. #spotlightondanny is the room:
Laugh track is loud. #fun keeps winning, with #meme , #comedy , #entertainment , and #interesting right behind it.
Picture desk: #nature and #photo from the North Cascades via
Tech and money lane: #technology from
Heavier wire, said straight:
Also in the mix:
Who filed from the user side:
Want the next rundown while it is still warm? Subscribe to
Hottest tags: #fun , #earn , #entertainment , then #spotlightondanny , #comedy , #technology , #meme , and #nature .
Cake table first. #spotlightondanny is the room:
Laugh track is loud. #fun keeps winning, with #meme , #comedy , #entertainment , and #interesting right behind it.
Picture desk: #nature and #photo from the North Cascades via
Tech and money lane: #technology from
Heavier wire, said straight:
Also in the mix:
Who filed from the user side:
Want the next rundown while it is still warm? Subscribe to
1
1
1
0 reactions
How Stripe uses graph search and state machines to auto-remediate a global database fleet
#technology #programming #dev
#technology #programming #dev
0 reactions
Junior dev here: how did you get from "code that works" to senior-level Python?
I'm a junior developer at my firm, about 1–2 years in. My code works, but when I compare it to what our seniors write, theirs is cleaner, easier to follow, and holds up better when requirements change. I want to close that gap deliberately instead of hoping it happens over time.
For context, I'm comfortable with functions, loops, classes/OOP, and basic testing. I mostly work on automation and scripts, and I've noticed my scripts tend to start small and turn messy as they grow.
I'd love advice on:
What actually separates senior-level Python from junior-level? Is it mostly design, naming, testing, or something else?
How do you structure automation code so a quick script doesn't turn into an unmaintainable mess?
Books, codebases, or resources that changed how you write code. Are there open-source projects worth reading?
Habits that helped you most, like code reviews, refactoring old code, or writing tests first.
Common junior mistakes you'd tell your younger self to stop making.
Thanks in advance, I really appreciate any pointers.
#programming #dev #technology
source
I'm a junior developer at my firm, about 1–2 years in. My code works, but when I compare it to what our seniors write, theirs is cleaner, easier to follow, and holds up better when requirements change. I want to close that gap deliberately instead of hoping it happens over time.
For context, I'm comfortable with functions, loops, classes/OOP, and basic testing. I mostly work on automation and scripts, and I've noticed my scripts tend to start small and turn messy as they grow.
I'd love advice on:
What actually separates senior-level Python from junior-level? Is it mostly design, naming, testing, or something else?
How do you structure automation code so a quick script doesn't turn into an unmaintainable mess?
Books, codebases, or resources that changed how you write code. Are there open-source projects worth reading?
Habits that helped you most, like code reviews, refactoring old code, or writing tests first.
Common junior mistakes you'd tell your younger self to stop making.
Thanks in advance, I really appreciate any pointers.
#programming #dev #technology
source