What trips me up is questions in meetings that are onerous.
1,086 karma · joined February 8, 2021
What trips me up is questions in meetings that are onerous.
In terms of day-to-day usage, it depends on what kind of development you do and in which sector. For example, web developers tend to not worry about math almost at all, video game developers, especially game engine one's deal with math a lot.
Sector is really important as well, if you work for a health insurance company you might need to understand statistics, finance companies can deal with large data set and algebra level financial formulas.
Of course, I'm speaking in generalities. In my opinion learning math is useful, in some jobs it's a necessity, in others it's not.
The author has no idea what is a programming language, why it exists and where it is used. To suppose that Java is equivalent to python only because a lot of programmers work on the most simple part of an application is totally wrong. It is as to suppose that a bycicle is better than a Caterpillar Miner only because there are more people that use the bycicle than people that drive a Miner. Ok.
Ultimately, I consider data points like that very ephemeral, and it's almost useless after the fact.
I also like having the story id as part of the commit message so merge requests can be connected to stories. It gives a better overall picture of what took place.
Every blogger, small gonzo roleplaying books, big companies using OGL1.1 had to take a look and figure out what 1.1 was going to do to them. Multiple companies are already changing their licensing moving away from OGL.
I don't blame them, no one wants a ticking time bomb in their hands. Most people use OGL 1.0 as a way to protect themselves from being sued as a just in case. Now they know that protection could disappear, so they have to adjust regardless.
It appears that internally it has created huge rifts based on Twitter posts from employees. Some of them going full tilt against Wizards of the Coast and Hasbro, including big D&D 5e figures.
My age group, mid 20s during Netflix creation, everyone I knew have a Netflix DVD subscription. We were raised with VHS rentals, so DVD rentals were the natural next step when DVD players got cheap.
Netflix allowed a huge library of DVDs to be rented. You could have 3-4 DVDs on rotation for a rather cheap price.
This happened when Blockbuster would charge you $5 per movie, and Netflix would charge $10.99 for unlimited DVDs, but you could only have 3 DVDs checked out.
That's why Netflix was huge and killed Video Store rentals.
Before I proceed, I have to say that in my personal opinion piracy makes sense when it comes to media, as in music, movies, shows. I feel like application piracy is a different thing. Mainly because with an application you use it a lot, while media, you own a CD, you can listen to it, but it won't be daily for years (like Windows for example). I'm also against book piracy, with the exception of university books because it's predatory.
If I did pirate stuff it would for the exact same reasons why I would have had a pirate FTP server in the 90s.
In the 90s it was because you had to pay multiple fees (or had to buy multiple CDs etc) to get access to media. If you lacked the money, you had no access. As a poor college student, it made sense to use piracy bridged that gap financially.
In the mid 2000s you basically had to use Netflix and Pandora/Spotify/Internet Radio, I have to pay a few fees, and have access, or watch small advertisements and get it for free. At that point piracy would be doing more work to get the same result.
Nowadays you have multiple services, they each have tiny niches which is exactly how Cable TV works in the States, and why piracy made sense in the 90s to begin with. If you like 4 TV shows, there are probably in 4 different streaming apps you need to use. All with their own fees. To make things worse services like Hulu, and others are still going to have advertisements. Essentially you are paying the services to watch a show, and they make money a second time by forcing advertisements down your throat.
That's BS. Maybe I just don't like spending money.
There is another problem about ownership. Anything in the cloud, you don't own, even if you paid for it. $4.99 to get this movie online annoys me. I have no control of it. I can't resell it. Sometimes it's hard to even tell what you own. I rather have it in my hard drive, then I can do what I want to it.
Ultimately though, piracy is about greed and money, both for the pirate and the services that get affected. In the 90s it was about freedom of access. That's not as much an issue case anymore.
Specifically, if things are not "working", I expect the developers to understand how their code works and what it needs to function properly. I'm constantly surprised by how much developers don't know about the app they write code for.
I'm not asking for your intellectual capital because I want to sue you. I want to understand how the app comes up.
The main problem I'm usually trying to solve is, apps are just packages of stuff, if I can deliver 1000 packages no problem, but one doesn't deliver is it the package, the address it got sent to, or is this some brand-new package requiring a different way of handling it. I need the package sender to explain to me what it contains.
On another note, @klodolph, if you are getting paged a lot, then your SRE needs to improve. Perhaps you were slightly exaggerating, but I consider any escalation to SRE personnel a failure on the SRE side. It's kind of a brutal metric to follow, escalations as close to 0 as possible. An interesting thing that happens if you try hunting for it is you will realize 80% of your calls come from 1 or 2 things. Addressing them will make developers happier and SREs happier.
You talked about having a positive mental attitude being really helpful in overcoming shortcomings. This implies you didn't start that way and you learned the behavior.
Can you explain the thought process you adopted? I sincerely struggle with having a positive mental attitude (see I did it again) but I have recognized it's a huge indicator of a better life (social, work, family etc)
- A fan
I even thought that maybe I had to make everything light themed so there is no contrast between pages /apps but it doesn't help.
This is purely a personal observation of how my eyes work.
Or Docker images have K, L problems that Podman doesn't have. However Podman has W issue so you have to decide which pain you want to live with.
That kind of stuff.
If not, which is what the diagram implies, how do you handle two branches with two PRs trying to get merged in, since there is a chance that they will create conflicts with each other. Do you force branch tests sequentially?
It all sounds good. Compact keyboard has always appealed to me, so did ergonomics, I bought a split keyboard (36 keys) with Miryoku layout and went to town. I lasted about 1 month and quit.
What happens is the amount of keys you have to type concurrently increases forcing your fingers in weird positions.
For example, typing the following 48 characters
if (needle in [a, b, c]) {
println('found it')
}
In a standard keyboard you have to press 53 key presses (parenthesis is Shift+9 so that's two keys for a single parenthesis etc)In a Miroyoku layout it's 59 key presses. This might not sound like a lot but it's a ~10% increase.
It also doesn't account for a very big problem, arrow key navigation for non VIM users. Since pressing the arrow keys requires two button presses in smaller keyboards, and done repetitively it's a huge slow down in navigating text. Now there are solution to this, most IDEs can support VIM keybinds, or have their own hot keys to skip words etc. To me the arrow key navigation is what got to me long term and I opt4ed out of it.
I know Microsoft gets flack in HN, but I find this document a pretty good primer on API design and decisions you should make: https://docs.microsoft.com/en-us/azure/architecture/best-pra...
Now if you have to consume an API you have no control of make sure you are mocking at the right layer, aka mocking the response, not the actual call to the API.
Granted, I have specific code tells, which helps, but like the article mentions I have forgotten the why or the bug that I fixed that required specific changes.
I have been journaling daily for close to 20 years, with the exception of a few breaks and skipping journaling in really busy days.
From my personal anecdotal perspective I feel that overall it's a positive experience. I've tried multiple mediums, Evernote, Workflowy, Pen & Paper, Google Docs, and countless of journaling apps. I find pen and paper the best, probably because I can parse my thoughts better when I write them down over typing them. Even though typing is much faster. There is something magical about making a moment for yourself with a fresh cup of coffee, some music, a pen and a journal.
I've also experimented with the type of content I want to journal. It feels like the standard is to write about your day. I find that the least fun way to journal. Albeit at times my personal day to day life bleeds into my journaling, I prefer writing about my thoughts, what I'm struggling with, debating to do, what I'm trying to improve.
Essentially for me, journaling serves as part self-therapy, part life strategy writing, part goal planning and blocker removal strategies. I can analyze my actions and their side-effects. Do it long enough and you start seeing patterns in your way of thinking, or you will catch yourself writing about the same thing yet again. I strongly suggest you don't just write when you journal, create flowcharts, make bullet lists, underline things that you think are important. It's a very undervalued thinking tool.
Usually when I talk to friends about journaling the common deflection is "I don't have that kind of time". Here is the thing, it's ok to write just one paragraph. Sometimes even a single sentence. I have journal entries that just say something like "I have nothing to talk about". The thing is you are building a habit. Most of my journal entries are about 2-3 paragraphs, about 10 minutes of writing. Occasionally if I feel overwhelmed, or troubled by something I might write for an hour. Other times I might write a short journal entry and 12 hours later make an update with new thoughts.
I hope this helps someone thinking about journaling.
To echo the linked article, what's interesting is reading past entries and realizing how you are often wrong, but tenacious, stubborn, a dreamer, someone that doesn't give up...because you are still doing it...you are still here, fighting.
I try to keep my code changes small. I rather have 4 changes in four different PRs, than a single one. Have you ever opened up a PR, saw 25-100 files changed and you just moved on instead of going through it?
Also, I will add a small explanation of what I'm trying to solve, and if I did something "smart" I'll explain why.
Finally I keep a small list of people that tend to approve my changes fast and ping them if enough time has passed.
On the flip side when I see a PR, I will let people know that I'm looking at it OR that I will look at it at a certain time and they should ping me if they don't hear from me (approval or comments). Also I have compiled a checklist that I follow for my PRs which speeds up the process, at least for me.
My PR checklist has three sections, what I should evaluate, how I should communicate and how to write things in the PR itself. It's an accumulation from things I have seen in HN, the Google Code Review process, and reminders to myself. I tend to sound more authoritarian than I mean to be, so it's a reminder to be more gentle.
# Checklist
1. Design.
1. Functionality - Does the code do what it's supposed to do?
1. Complexity - Are individual lines, functions, classes too complex (aka hard to understand quickly).
1. Maintainability - too tightly coupled? Configurations hard-coded.
1. Comments - are comments actually necessary, they should explain why. Are there any comments/TODOs that can now be removed?
1. Documentation - has the appropriate documentation been updated
1. Good Things - comment on the good things as well
1. In general, favor approving a CR once it's in a state where it definitely improves the overall code health of the system being worked on, even if it's not perfect
## Communication
* Accept that many programming decisions are opinions.
* Ask good questions, don't make demands (what do you think about naming this `user_id`?).
* Good questions avoid judgement and avoid assumptions about the author's perspective.
* Ask for clarification ("I didn't understand. Can you clarify?").
* Avoid selective ownership of code (mine, not mine, yours).
* Avoid using terms that could be seen as referring to personal traits (dumb, stupid). Assume everyone is intelligent and well-meaning.
* Be explicit. People don't always understand your intentions online.
* Be humble (I'm not sure - let's look it up).
* Don't use hyperbole (always, never, endlessly, nothing).
* Don't use sarcasm.
* Keep it real. Be yourself.
* Talk synchronously. Post a follow-up comment summarizing the discussion.
## Reviewing Code Communication
* Communicate which ideas you feel strongly about and those you don't. (Nitpick: )
* Identify ways to simplify the code while still solving the problem.
* If discussions turn too philosophical or academic, move the discussion offline to a regular Friday afternoon technique discussion. In the meantime, let the author make the final decision on alternative implementations.
* Offer alternative implementations, but assume the author already considered them. ("What do you think about using a custom validator here?")
* Seek to understand the author's perspective.
* Sign off on the pull request with a or "Ready to merge" comment.
* Remember that you are here to provide feedback, not to be a gatekeeper.Tests don't catch that. Unless the tests are written by someone other than the developer, which honestly I haven't seen.
As a contrived example if a developer interprets that they need to multiply instead of add, their method and tests might work 100% but they will give the wrong result. Even worse, in certain cases 2 * 2 = 2 + 2 so they will give the right result with the wrong calculation.
It helped a lot, but then 1 year old I stopped using it. The problem is GTD is too heavy process wise. There are a lot of little actions you have to take, which at times end up taking as long as next action items since action items will continue to grow.
All GTD web apps always left something out that I did. I lost count how many different websites I tried. I count that as a net productivity loss.
There are a few solid GTD ideas that I have stuck with, but my process has become a lot simpler that it's almost a non process.
Things that GTD is right about
1. Inbox zero
2. Doing a todo dump in a list
3. Having a small number of "in" work
I still follow these three ideas. The rest of my process is a lot more present oriented.
Remote Controlled land and water units would also work.
There are multiple reasons why it's the future.
1. Cheap to make
2. Can be smaller since they don't have to have space for humans to sit in them, which might increase ability to carry things, longer range etc.
3. Because humans don't have to be inside of them they can also go a higher speeds, maneuver faster without human body limitations
4. If a drone goes down, the drone pilot can man another one. All that training and knowledge is retained. Human operated vehicles have a high probability of losing their occupants.
5. If 5,000 drones get destroyed, it's lost money. If 5,000 military personnel gets killed it appears much worse in terms of optics, value of life etc.
It adds noise to the code with no actual benefit. If a TODO is outdated it actually becomes a false flag, it's like a comment that doesn't reflect the code changes so now it adds to the confusion instead of alleviate it.
Personally I add // FIXME while writing code but I make sure to remove all of them prior to creating a merge request. It's my way to track outlier issues that I will turn around and fix as I parse my code. If I find a // FIXME that deserves to be its own enhancement or a future TODO I will capture it as a story. My org is Agile story driven which is why I put it there.
Perhaps adding TODOs for a personal project is fine. However for repositories that multiple developers touch a TODO at best is noise, at worst a point of confusion.