Time for #DevDiscuss
Tonight's topic is Unwritten Dev Rules
So let's start the conversation:
What underlying rules govern our work?
Which are good and which need to be dropped?
Time for #DevDiscuss
Tonight's topic is Unwritten Dev Rules
So let's start the conversation:
What underlying rules govern our work?
Which are good and which need to be dropped?
Write code as if you’re the one who will have to refactor it six months from now when you don’t remember anything about why you wrote it like you did. #devdiscuss
It might be obvious, but BE KIND.
We’re in this together. Look out for one another and lend a helping hand when possible. If you can spend five minutes to save someone an hour—do it!
#DevDiscuss
Time for #DevDiscuss
Tonight's topic is Unwritten Dev Rules
So let's start the conversation:
What underlying rules govern our work?
Which are good and which need to be dropped?
The rules I care about:
- Build secure products
- Build accessible products
- Deliver value early and often
- Be nice to each other
Pretty much everything else is negotiable. #devdiscuss
Time for #DevDiscuss
Tonight's topic is Unwritten Dev Rules
So let's start the conversation:
What underlying rules govern our work?
Which are good and which need to be dropped?
Time for #DevDiscuss
Tonight's topic is Unwritten Dev Rules
So let's start the conversation:
What underlying rules govern our work?
Which are good and which need to be dropped?
When I hear about "rules" I think of places where process is the goal, rather than the means to achieve an outcome. I think of orgs where teams are disempowered. Where trust doesn't exist. #devdiscuss
Time for #DevDiscuss
Tonight's topic is Unwritten Dev Rules
So let's start the conversation:
What underlying rules govern our work?
Which are good and which need to be dropped?
Why would you pretend like you know something that you don't? Doesn't that put on false expectations?
Better to admit you don't know it with the attitude that you're willing to learn it (if you are). Keeps timelines realistic.
#DevDiscuss
I believe it's more productive and healthy to think of "principles" that guide behavior, but are flexible. "Rules" are rigid, inflexible things that are most often unnecessary #devdiscuss
The most thing about this community is let's learn/share/help other people. The bad thing is when someone newbie doesn't understand things they are mocked by Senior.
Let us not make that here! Let's help mom code in her 50s, let's help a brother code in his 20s etc. #DevDiscuss
Time for #DevDiscuss
Tonight's topic is Unwritten Dev Rules
So let's start the conversation:
What underlying rules govern our work?
Which are good and which need to be dropped?
Most of my work is done remote but at one job we got together a conference. So we had the rule for every build you’ve broken that year you buy a round #DevDiscuss
Expecting someone to have the same level of productivity everyday. There will always be spikes and lows that need to be considered. Especially the lows #DevDiscuss
Time for #DevDiscuss
Tonight's topic is Unwritten Dev Rules
So let's start the conversation:
What underlying rules govern our work?
Which are good and which need to be dropped?
Time for #DevDiscuss
Tonight's topic is Unwritten Dev Rules
So let's start the conversation:
What underlying rules govern our work?
Which are good and which need to be dropped?
My unwritten dev rules:
-be honest if someone brings up JavaScript things that you don’t know
-ask for help instead of struggling
-own up to miscommunication
-I dont care how well you know that command in the CLI, just write it down!
#devdiscuss
Time for #DevDiscuss
Tonight's topic is Unwritten Dev Rules
So let's start the conversation:
What underlying rules govern our work?
Which are good and which need to be dropped?
Premature optimization might be the root of all evil, but that doesn't mean you should be content with slow code. Optimize what you can when you can, but don't sweat over things that don't matter.
#devdiscuss
Time for #DevDiscuss
Tonight's topic is Unwritten Dev Rules
So let's start the conversation:
What underlying rules govern our work?
Which are good and which need to be dropped?
I was good team moral thing at that shop not the sort of thing that works everywhere. Many of the people I’ve work have had things this That one was kind of fun but build breaker penalties suck #DevDiscuss
code without tests is snake oil.
when you write code, your audience is the humans who will read it after you, just as much as the compiler. perhaps more.
play nicely. share.
don't quite give 100% at work; you'll have no reserve when shit goes down.
#devdiscuss
One rule I try really hard to live up to (but often fail): if you're stuck for more than 15 minutes, ask someone for help. Nobody has time for you to thrash around. #devdiscuss
Time for #DevDiscuss
Tonight's topic is Unwritten Dev Rules
So let's start the conversation:
What underlying rules govern our work?
Which are good and which need to be dropped?
Take care of yourself. It can be really easy in our line of work/hobby to get hyper focused at the expense of everything else. Fatigue, burnout, and isolation aren’t fun (been there).
#DevDiscuss
Time for #DevDiscuss
Tonight's topic is Unwritten Dev Rules
So let's start the conversation:
What underlying rules govern our work?
Which are good and which need to be dropped?
Time for #DevDiscuss
Tonight's topic is Unwritten Dev Rules
So let's start the conversation:
What underlying rules govern our work?
Which are good and which need to be dropped?
Another one: show some appreciation for your leader, especially if they are a patient and nice one. I try to get a coffee or a beer for mine because he is great #devdiscuss
rules that need to be dropped: micromanaging. the best managers organise but keep out of the developers' ways as much as possible.
(obviously sometimes you have to step in. but that's exceptional.)
#devdiscuss
Always remember that future you will hate past you for not documenting that one little thing that you think you will _totally_ remember. You will probably forget it 3 months from now let alone 3 years from now. #devdiscuss
Time for #DevDiscuss
Tonight's topic is Unwritten Dev Rules
So let's start the conversation:
What underlying rules govern our work?
Which are good and which need to be dropped?
1) Devs can be a demanding bunch. Don't hate on your platform/core/devops teams, they're often understaffed and under-appreciated.
2) "X is better at what need than Y" Opinions are useless. A reproducible test is proof.
#devdiscuss
I totally agree with this. But, only when project managers appreciate that old devs sometimes leave strangely documented code and work-around patches that new devs will need to make sense of. Things will often break before they get fixed. Don't blame new devs either! #DevDiscuss
Things you can do when a former coworkers code breaks:
Complain that the code wasn't written/documented/whatever well enough then set team standards to fix that problem. #DevDiscuss
The rule of three
A reusable component should be tried out in three different applications before it will be sufficiently general to accept into a reuse library.
#DevDiscuss
The rule that says programming is also your hobby. That you have a GitHub repo with real projects.
Professional means spending some time keeping up. It doesn't have to be for fun.
#devdiscuss
Also, solving something in a more readable way is better than the clever way. Let the compiler do the optimization until you have to (premature optimization is the root of all evil) #devdiscuss
Time for #DevDiscuss
Tonight's topic is Unwritten Dev Rules
So let's start the conversation:
What underlying rules govern our work?
Which are good and which need to be dropped?
write tests. it doesn’t matter if you do it before or after (though I would urge you to do it before), just as long as they get written before that code goes to production.
that said, not every line of code needs to be tested, but make sure it’s a conscious decision. #devdiscuss
Let’s drop:
Developers should always write unit tests
Let’s start:
Write the right kind of test for the functionality.
Sometimes controllers with 8 dependencies don’t need unit tests, they need integration tests.
#DevDiscuss
That is the worst! I know several developers who on complex code will document parts of it in comments and then link to the ticket/wiki page with more information, which I think is ideal. #DevDiscuss
There's a difference between liking what you do and making it a hobby. If you don't like dev, the job will kill you. But you're allowed to do other stuff. #devdiscuss
Embrace
- Capture your assumptions, e.g., tests, specs, comments
- Do no harm
- Write readable code
- Write informative docs
- Reinvent the wheel when ur context is different
- Try not to depend on external libraries
- Prefer standard libraries to external libraries
#devdiscuss
I finally broke and bought myself an Apple Watch.
Not sure this is a win, or even an announcement, but sometimes you just gotta get something out of your system.
So far, I kinda dig it! Never thought I'd be able to make an actual phone call from my wrist watch... #DevDiscuss
Drop
- No one reads documentation
- Code/Test/Software is the documentation
- Latest tech/language/library/tool will solve the problem
- Software is all about technology and very little about people.
#devdiscuss
