I've joined @protonmail 2 years ago, and this was the best move I did in all my career: great colleagues/challenges/achievements... and more important: giving sense to our jobs for an ethical mission.
Any questions on any position, don't be shy: ping me, feel free to ask. It always starts with a simple conversation, and it ends with super nice opportunities and achievements.
I like how the tutorial is written. Starting by doing everything the long way, to then show how the framework solves this for you so you can delete a bunch of code. It's risky, specially for impatient people who just want "the magic", but definitely a good way to highlight the convenience of the tool while showing the different layers it is made of.
I've been a YNAB user for years, so at least I can say that the product is great 🙂
(And for the record: I'm not saying barebones in a bad way, just as an observation)
I'm following Django's tutorial step by step, since at work it's being used in a couple of our apps and I don't really know it. It's the first framework I learn since Ruby on Rails… 7 or 8 years ago? It's interesting to see how each one solves the common problems and the room they leave for creativity, or even how hard the conventions are enforced.
So far I'm feeling that Django is very barebones, but it could be a faux impression. We'll see!
(back to the tutorial, now)
@carlesjove It's interesting seeing this. I have made a similar observation with a different conclusion:
Over the years I have learned there's so much more to software development than coding. Every week I'm discovering new facets of computing and the tech that surrounds us. It's fascinating. There's always something just around the corner to feed my curiosity.
That being said, I'm lucky enough to work with people who (so far) can share a laugh when I say that I don't know what the hell they're talking about.
I don't know about you, but I feel that as a programmer there's more and more stuff I have to know about every year. Sometimes I'm more blocked by everything surrounding code (the containers, the vpn, the whatever thing this is i had never heard about before, the config of who knows what) than the code itself and what i'm trying to solve there. It's exhausting.
Fuck. How many typos in this toot 🤦 Gosh.
(Now's when someone says "man, this is programming 101" and I'm like 🤷 )
Yesterday I learnt that in Python, modules can be reloded at run time. Super useful when doing stuff in a repl while editing the code.
So imagine you have loaded a module
> from some.path import mymodule
And you have edited the code in mymodule but you don't want to start a new session and set everything up again. You do:
> import importlib
and boom, the new version is loaded. How cool is that?
Ahhhhh… Nice. Green dot besides the red means that deployment fixed the bug.
Time to get drunker and not think about code until Monday.
You're a team manager. Deployment Friday night went wrong and dev says "sorry, I was drunk". Watcha do?
Good thing my team mates are all on birdsite instead of here
(Please don't answer)
I mean… it's Friday night already. What could go wrong?
Solutions Engineer at Localistico. Open Source enthusiast. Punk-rock attitude.
He/Him | They/Them
This Mastodon instance is for people interested in technology. Discussions aren't limited to technology, because tech folks shouldn't be limited to technology either!