mdbauman
Sad to say I've only recently come to this realization. It applies to pretty much anything, whether it's building a business or exercise or learning to draw. And if your motivation can't sustain you long-term, change your perspective so that you have a motivation that will let you see it through. "Make something cool and get rich" doesn't take you very far once you step back for a moment.
With the separate numpad you can position it just above the mousepad so it's still easily accessible, but you have minimal movement distance between typing and using the mouse. To me it's the best of both worlds, and it's strange to me that it isn't more common to sell the two as a package. I suppose the assumption is that people who want numpad will just buy a 90% keyboard and numpad separately.
I was drawing a lot at the time, and many of my portraits with no nudity at all were deleted. That was my sign to leave.
Whenever I've discussed this, the common theme is that business users continue to request features that would be easily achieved in the low-code platform being used. It's hard to blame them; that's been standard procedure for them for their entire career.
But if you're not strict about saying "no", you still end up writing all the same methods but now on top of that you have a GUI that's not providing any value. Or maybe worse, your developers end up maintaining all of the low-code stuff too when they could have just written the code, switching context pointlessly and (probably, depending on the platform) not using source control.
One thing that jumps out at me is the assumption that compile time implies wasted time. The linked Martin Fowler article provides justification for this, saying that longer feedback loops provide an opportunity to get distracted or leave a flow state while ex. checking email or getting coffee. The thing is, you don't have to go work on a completely unrelated task. The code is still in front of you and you can still be thinking about it, realizing there's yet another corner case you need to write a test for. Maybe you're not getting instant gratification, but surely a 2-minute compile time doesn't imply 2 whole minutes of wasted time.
This is wonderful criticism! It's thoughtful and well-researched. Hell, even I'm inspired to finally dive into Godot's internals, which I've yet to do despite following the project for several years. I hope this inspires even more contribution and constructive criticism.
I can't confirm his thoughts on Perl and I haven't interacted much with Ruby, but the Python community is definitely welcoming and patient in my experience. I wouldn't be surprised if this was a significant factor in Python's prevalence over Perl, Ruby, or anything else.
Fast forward 8 or so years. We no longer do trivia, but get together just about every week along with the siblings, childhood friends, girlfriends, and wives that have joined us over the years.
It's a little strange to think of how different my life would be had I not been at that bar on that night, but that's how these things work: you put yourself in a situation where something social is going on, and all that's standing between you and making some new friends is saying "yes."
I've had a few of these over the years that I take to coffee shops/bars to work. It's nice not to feel nervous about a $1000+ investment just because the server is coming around to refresh my water.
Apple has made seemingly made the most progress toward this and it isn't hard to imagine someone plugging their iPhone in to a screen when they arrive at work and resuming their Excel spreadsheet with the connected keyboard, no different than the company-issued laptop today. But I don't see what incentive Apple has to make that a reality when they can keep selling people two separate $1000+ devices.
Edit: I would love to be proven wrong, so any opinions/examples to the contrary are very welcome.
I was a little sad to read that Mills in fact lives in Delaware, not Nebraska. I always had a sneaking suspicion that this comic was NTP-related.
This is mostly relevant because when people talk about Lua's speed, they're usually talking about LuaJIT [1] which (iirc) was based on 5.1 and backported many 5.2 features.
So, if you're someone who's decided to use Lua for a specific use case, you may want to see if your target specifies a specific Lua version (ex. Roblox, LÖVE, PICO-8, OpenResty are mentioned in this thread and all use either LuaJIT or a subset of 5.1), or if you expect to need the performance of LuaJIT in the future.
Edit: formatting
If you're "pirating" a game, I imagine (because this is why I pirated games in the pre-Steam days) it's because you can't afford to buy it or you refuse to give the publisher/developer your money on principle. Either way, you're not a potential customer. So sure, this may result in less emulation but not necessarily higher sales.
In particular, a sibling comment mentions Kotlin. The docs[2] link to a project that adds Kotlin bindings https://github.com/utopia-rise/godot-kotlin-jvm
[1]https://docs.godotengine.org/en/stable/getting_started/step_...
[2]https://docs.godotengine.org/en/stable/tutorials/scripting/g...
I don't think I'd consider this guy a frontend developer given that he couldn't be bothered to learn a framework that falls within his job description. But we also had a UX team to actually design the visuals, so I don't think I'd put him in the designer camp with them either. What was he? "Lead CSS Guy?"
> A specific combination of nucleotides is first modeled in simulation to be the correct size to handle the target virus
Although my normal keyboard does still have function keys and a numpad, I like being able to map annoying shortcuts to individual buttons. For example, Photoshop's "Merge Visible Layers" (default Ctrl+Shift+E) is hell on my wrist, so I map it to a button on the MIDI controller.
It's also nice having extra buttons to access F13-F24 for whatever behavior I want since virtually nothing uses them by default.
If you're considering reading some of these but are specifically interested in the developer's point of view, I suggest reading some reviews and/or a bit about the [author] so you know what you're getting into.
For example: I liked the ZZT book very much, but that may be because I was briefly involved in the ZZT community in the early 2000s; it feels good to have a part of my history written down. If you've just read the Spelunky book (written by the developer Derek Yu) and are hoping the ZZT book is something similar from Tim Sweeney, you [may] be disappointed.
If I remember correctly, the "hacking manuals" section is what inspired my reading for much of middle school. I wonder how many other 12-year-olds turned in a book report on Neuromancer to a horrified teacher because of this post?
Joking aside, this does sound like something I'd actually use and the formatting on the resulting document is very pretty. And just to let you know, your "Buy us a coffee" link gets jumbled at lower screen widths.
I'll buy that on average, brainstorming is an inefficient way to improve the quality of a product, especially if all members of the team are reasonably knowledgeable about the subject. But as the article mentions, that's often not the case.
It may not always or even often result in a better product, but there's definitely value in finding those outlier projects where you can save time and money with an approach that would be obvious to someone with more familiarity with the subject. It's hard to know if this is the case beforehand, so it may be a sensible default to hold a short brainstorming session for any project so your team at least has the opportunity to identify areas for improvement.
Edit: formatting