Laughs in object
December 8th, 2009 - Motorola Droid successfully rooted ... [granting] root access on the phone using a terminal emulator. This is how I learned bash which inevitably pushed me into pursuing proper Computer Science.
Interesting perspective I hadn't considered before, thanks for sharing. Also, not sure where the Java 7 thing comes from, but I run Java 17 with gradle/kotlin non-android, works very well in IntelliJ, outside of consuming a million gigs of ram lol
December 8th, 2009 - Motorola Droid successfully rooted ... [granting] root access on the phone using a terminal emulator. This is how I learned bash which inevitably pushed me into pursuing proper Computer Science.
It covers each and every line of the source code, each and every conditional statement in the program and every loop otherwise known as iteration in the program.
I think it is important to note 100% code coverage ("covers each and every line") does not mean the tests are good tests.
The most simple way of explaining the cloud computing is storing, accessing, and processing data over the internet instead of using a traditional client server architecture.
Just because your compute is "in the cloud" doesn't mean it isn't a server, and it definitely can still be client/server architecture
Cloud provider hosted server accessed by client = client/server architecture
Interpreted language != Compiled language
Great call out.
Definitely their products. I think things like buck2 are rad.
~~test~~
Like this ~~test~~
Edit: You said subscript not stikethrough 🤦
Although I despise their software, I do enjoy their engineering blogs, thanks for sharing.
I have found it quite effective while pair programming (senior to junior mentorship) to say OUT LOUD exactly what I'm changing and why I'm changing that. This allows others to more easily follow your train of thought and can lead to good discussions rather than turning PRs into essays.
However, as other comments have mentioned, this can get exhausting.
RandomDevOpsDude
joined 1 year ago
I have been using "gaming" keyboards for coding for ~10 years now. The only thing to be wary of imo, is keebs that have "extra customizable keys" on them and break conformity from a standard layout. Depends on the device, but Logitech will call them "G keys", for example, and often stick them on the far left of the board, left of tab/caps/L shift. Makes life a lot more difficult if not gaming.
Outside of that, I think calling something a "gaming" keyboard is more of a marketing tactic to up the price. It's hard to not recommend mechanical, but that sounds out of budget and often hard to do wireless/bluetooth, but personally I think mech is the top priority.
What I have seen a lot of peers do is wait to see whatever keyboard the get in office, then buy the same one for home for consistency, rather than dragging a personal one back and forth. Often companies will offer basic boards like logitech K270, K350, or K650. Not amazing, not terrible, and most likely fit in your described criteria.