I don’t have the name handy, but there’s at least one plugin for vim that shows buffer previews in a popup. I’ve got it mapped to leader-sb (for “show buffer”).
So far I haven’t been brave enough for that feature. It’s either “that main place yank goes”, “system clipboard”, or “that place that makes it disappear” for me
You can see all registers in use with :registers, to paste from a register say "2 in insert mode use key combination <ctrl-r>2 or in normal mode "2p. You can check out more in :help registers. Unnamed register or “” is the system clipboard I think. To copy texts in a register you can prepend yank (/delete/cut, etc.) with that register "_ (for black hole register[^black_hole]) This is for neovim. Have keybinds for them and there saved you a plugin :D
[^black_hole]: Text yanked in this register is gone, i.e. it’s not saved in any register.
Please tell me it doesn’t still happen when you emulate a different day of the week. Or is that non-trivial to even do because of technical debt? Either way, RIP weekends.
If we reject the theory that it could be someone’s elaborate revenge, Saturday may be the first day of the week that may become workday or non-workday because of incorrect assumption about the first day of the week. If everywhere but one place in your software the day numeration is correct it would be a hard bug to spot.
Also, if it is in Java, I vaguely remember there being a lot of ways to express weekday, so a lot of ways to shoot off your foot (solely on Saturday)
For bonus points, this failure is in a cron job that sends out recently queued messages. It runs once every ten minutes - last weekend we had 12 failures: four were in a cluster on their own, one was in a run of two, and six were in a single continuous run.
Please note that this server is unused by our business so no messages ever get naturally queued. Every day we sync the live production server to this server at about 9 PM - assuming an employee was queuing up a message before the snapshot is taken there might be a number of unsent messages in the snapshot - those messages will all be sent by the first cron job after the sync.
It is a wonderfully awful problem that has me wanting to pull out my luscious locks.
Yup, luck is appreciated and I’m trying to get more eyes but unfortunately I’m a senior dev that has the second highest seniority at the company so I feel guilty dragging others into it.
I’ve always hated recursion. It’s always seemed like a cutesy programming trick that’s not reliable in all conditions.
You could blow the stack in an edge case that you didn’t think of. So it should never be a standard pattern. It’s only good if you need to rewrite something for optimization and recursion is appropriate. But in many cases recursion is slower.
“Look at what I can do in 5 lines of code!” is for programming contests, not for anything important.
Do it dude - if you’re passionate about building a rich simulation game then there’s a good chance you’ll create something awesome. We’ve seen huge successes with Dwarf Fortress and Rimworld - those sort of complex simulations can be both fun and dazzlingly interesting in terms of their emergent game play.
It’s relatively simple to get started, just simulate one thing or render one simple 10x10 grid, and work your way up. Remember that video games take a lot of effort and set reasonable goals and milestones to recognize your progress… DF originally played on an, essentially, fixed map with no z-plane - wildlife was non-existent and sieges were just pre-planned events.
Same boat… But I had some success with low poly 3D models which I found are pretty easy to make. Learning a bit about color theory, how to match colors, as well as learning a bit about level design goes a long way. You can make a great looking game this way.
But my dream game is 2D pixel art, and I really suck at it.
You mean like an MMO where different maps are arranged in an infinite hexagonal pattern that’s randomly/procedurally generated based on different biomes, that also keeps track of how many players have entered/completed each hex and begins scaling down the difficulty in said hex and evolving it into a more peaceful zone, that way the higher traffic areas eventually form safe zones/towns for low level characters while low traffic areas encourage high level characters to visit and explore, with the highest level characters able to survive unexplored areas and expand the map for all players, all while having developer tools to specifically add unique dungeons/events/items directly to tiles so that the game doesnt feel a mile wide and an inch deep but instead as if the whole world map is alive and constantly changing?
Definitely some cool ideas there but how do you deal with the long term effect of the map becoming too big?
The bigger the map the more the defs would need to stretch their resources to adding cool stuff.
Also, at some point, the inner hexes will be essential all complete cleared and new players will have to wander for a while as soon as they level up a bit.
Unlocking a new hex would be fun at the beginning but how fun will it be after 100+ have been unlocked and any more just will inevitably just feel same-y because even the best defs will eventually run out of ideas
Welcome to Wayne’s World: The Game You find yourself in Aurora, Illinois, the hometown of Wayne and Garth. You’re on a mission to help them prepare for their biggest public access TV show yet. Scene 1: The Basement You’re in Wayne’s basement, surrounded by music gear, posters, and a comfy couch. Wayne and Garth are brainstorming ideas for their show, but they’re stuck. They need your help to come up with a killer opening segment. Do you: A) Suggest a musical number with Wayne and Garth performing a duet of “Bohemian Rhapsody” B) Recommend a comedy sketch parodying a popular movie or TV show C) Propose a special guest appearance by a local celebrity D) Suggest a “Top 10 List” segment, à la David Letterman Choose your response:
…
You have found the Encino Man Dungeon.
Encino Man: The Adventure Begins You are Brendan Fraser’s character, Link, a caveman who has been thawed out and is trying to navigate modern life in Encino, California. Your goal is to make it through each scene without getting into too much trouble. Scene 1: The Thaw You wake up in a block of ice in a backyard. You’re confused, hungry, and thirsty. You see a garden hose nearby. Do you: A) Drink from the hose B) Try to break out of the ice C) Look around for food D) Take a nap Choose your response:
LLM to generate ideas, history to check uniqueness
I had a cool idea that I completely gave up on because I tried to learn how to do it and realized what I was asking was so insanely complicated and time consuming that I couldn’t do it. I play a lot of games, I know what would make a good one, there’s just a gaping chasm between knowing and creating.
The problem is that this complexity isn’t just a one-off thing you need to get through. There’s a ton of details which matter, which you will not have thought through as part of your idea.
Many of these details, you will encounter as you write code. As in, you’ve just worked for three weeks on a feature and then realize a glaring problem in one of the details. Then you spend another week trying to find a solution. And worst-case that solution is to rip out that month of work and start fresh.
This has been my biggest learning from dabbling in gamedev for a while: Make a stupid paper model first.
Even if you spend a week glueing sheets of paper, and you don’t really even get that close to your actual idea, the more of these details you think of upfront, the higher your chance of getting anywhere (or scrapping your idea without wasting months trying to put it into code).
Well, and the other big learning was: Holy crap, gamedev is hard.
I know how to “code”. I’m a senior developer and have worked on multiple large-scale software projects.
The scope of the game I was trying to create, was laughable in comparison. As in shitty 2D, tile-based, turn-based.
I encountered performance problems like I’ve never had to deal with in my career, because it turns out the whole games industry is fueled by smokes and mirrors.
Know how ray-traced lighting is the craziest new technology? Yeah, that’s literally just a matter of hardware being strong enough that we can simulate lighting in the way it actually works. It’s conceptually simpler than the ever more sophisticated bullshitting we did beforehand.
have you ever smoked weed? ideas are cheap - even ones that seem good. ACTUAL good ideas are only proven good when they are implemented AND become successful.
That’s like saying a lot of banger songs could exist but the person doesn’t know how to write music.
Absolute delusional bullshit.
Verifying the idea is good is also part of the process. Play testing, making hard decisions, smoothing out jank, juicing up the experience… The whole implementation can make or break a game.
Not “great novels” but great “great world building”. I’ve seen some absolute bangers out there where the concepts, characters and even the overall plot blew my mind away. However, the authors couldn’t write decent dialogues or a coherent chapter of their life depended on it. So, most people wouldn’t be exposed to their ideas.
I had to learn that the hard way, but with a comic/manga idea I used to have.
Long story short: I worked way too long on an idea (almost 10 years), all while my taste etc. changed. It would have been way too hard to get it working after a while without a complete revamp of the whole idea, so I ditched it completely, maybe reuse elements and character concepts in other things, including video games (yes, they’re easier to make, unless your comic’s artstyle is stickmen figures).
The inability to detail the idea all the way down to the level were something concrete can be made from it kills it well before the lack of coding skills.
It’s like what separates having an idea for a book and writting an actual book that is enjoyable to read: there is no “knowing how to code” barrier in there and yet most people can’t actually pull it off when they try or it ends up shallow and uninteresting.
This is actually one thing I’ve been thinking AI and deepfake tech can potentially do good. Let’s say you have an idea and can code… You have an idea for music but no instrumental talent, so the best you can do is hum it. You can’t afford voice actors or other professionals.
Or maybe you’re artist with an idea who can storyboard but not code. Maybe you can make 2d designs but not 3D models, or aren’t great at animate.
But… there is software that can take what you say and change it to a different voice. It can animate a model to match the words. Similarly, software that could generate instrumental sounds from humming is possible. An AI can generate interactive dialog. It could also provide assistance in the generation of music, debugging of code, and eventually more advanced 3D modeling.
A lot of game design software is much more a GUI to an environment/model and triggers etc than stuff like writing hardcore backend C++ code etc. AI could take that even further.
Then add VR. Drop somebody into a blank-slate where they can create a whole world with a word, a gesture, and a great idea.
I’m not exactly sure what you mean. Doesn’t all dependency injection work the way I described?
Without being familiar with the framework, you can’t trace your way from the class getting injected into to the configuration, even if you’re experienced with the language.
I don’t think so. When I’ve seen it done it’s usually not been random values injected (except when those values are secret keys which should absolutely not be stored in code to begin with), it’s usually injecting a service. Another class, usually with a name that makes it easy to trace down. Like if you’re building an OrderService, that might take as a dependency an IProductService, which would have injected into it the class ProductService (personally, I don’t like the Hungarian notation that C# uses, but it’s a convention and my preference for sticking to strong conventions for the sake of consistency outweighs my distaste for Hungarian notation). That’s easy to find, and in fact your IDE can probably take you straight to it from the OrderService’s constructor.
It’s easy to imagine a hypothetical way that could lead to problems. But in all the code I’ve worked with, either that scenario is avoided entirely, or other context makes it absolutely clear which IProductService is being used.
It depends VERY much about the content and invitees of the meetings.
If you’re there to give your expert engineering feedback, awesome. If you’re there to receive the information you need in order to provide expert engineering feedback, awesome.
So often, I find, meetings are too broad and end up oversubscribed. Engineers are in a 2 hour meeting with 10 minutes of relevance.
There are serious differences in meeting culture, with vast implications oh the amount of efficacy you can juice from the attendees.
Ehhhh, depends on how your titles work, and I would argue that’s at least a little odd. Most senior engineers I know are ~50/50 code/oversight, at worst. Once you get to Principal or Staff, though, you’re lucky if you write 50 loc/week.
Senior rarely translates to something like architect anymore, it’s at least a level or two up from there.
The beauty of titles like this is that they’re absolutely meaningless.
You can’t compare them between companies, sometimes even departments, you can’t compare them between different industries, and you can’t compare them between countries.
I’m a senior, and my job is currently to sit in meetings most of the day to convince BAs, architects and other team’s leads not to make stupid decisions. The rest of my time I’m communicating the results back to my colleagues and writing escalation mails, because Steve again tried to re-introduce his god awful ideas that we shot down five times before and I’m hereby voicing my concerns in a business-like tone, but actually would want to exterminate him and his entire offspring.
My old project, however, was completely different and I actually spent 70% of my time actually writing code and 20% code-related meetings.
Not really, it’s really largely a technical discussion, but we have a distributed monolith (the architect calls it micro service…) so each change of an interface will percolate through the entire system.
No it isn’t - a senior engineer should be a technical track professional that’s excellent at their job - it’s likely there will be a fair amount of mentorship but that can take many forms including PR reviews and pair programming.
A technical lead, architect, or a front line manager is the one that should be eating meetings four to six hours a day. And absolutely nobody should be in eight hours of meetings a day - even bullshit C level folks should be doing work outside of meetings. Eight hours of meetings means that you’re just regurgitating the output of other meetings.
I’d clarify that having occasional eight hour meeting days isn’t bad, there might be occasional collaboration jam sessions that everyone prepares for… but if your 8-5-52 is solid meetings then nothing productive is happening.
It’s true. I even live in a place where the “Software Engineer” title actually does require a special designation, and I’m a “Software Engineer”, and I have no such designation, so there’s that.
Where I work, Senior Engineer is an IC role. They attend the same meetings as other engineers. Its the Staff+ Engineers and managers that attend more meetings (in ascending order)
I’ve worked in a few places, all with senior engineers, including myself as a senior engineer, all of which the senior engineers spent most of their time actually engineering. If I went somewhere as a senior and was told I was going to be in meetings all day, I would quit because that’s management, not engineering.
Of course there’s no point in trying to rationalize this 'cos these people use meetings to try justify their usefulness to the company (HR does the same with random activities), so you end up drawing red lines with invisible ink…
not my experience at all across 3 separate companies. Ime senior engineers are the highest level that still spends most of the day heads down most days, and that’s why I’m gonna stick it out at this level as long as I can.
Senior engineers write enabling code/scaffolding, and review code, and mentor juniors. They also write feature code.
Lead engineers code and lead dev teams.
Principal engineers code, and talk about tech in meetings.
Senior Principal engineers, and distinguished technologists/fellows talk about tech, and maybe sometimes code.
Good managers go to meetings and shield the engineers from the stream of exec corporate bs. Infrequently they may rope any of the engineers in this chain in to explain the decisions that the engineers make along the way.
Bad managers bring engineers in to these meetings frequently.
Terrible managers make the engineering decisions and push those to the engineers.
People in the technical career track spend most of their time making software, one way or another (there comes a point were you’re doing more preparation to code than actual coding).
As soon as you jump into the management career track it’s mostly meetings to report the team’s progress to upper management, even if you’re supposedly “technically oriented”.
Absolutelly, as you become a more senior tech things become more and more about figuring out what needs to be done at higher and higher levels (i.e. systems design, software development process design) which results in needing to interact with more and more stakeholders (your whole team, other teams, end users, management) hence more meetings, but you still get to do lots of coding or at least code-adjacent stuff (i.e. design).
I’ve worked for startups too; everyone does everything all at the same time! Let the chaos reign! But it is fun in its own way.
I work for a large company now after the startup I worked for was acquired. Hierarchy, bureaucracy, layers, we’ve got it all. For worse and for better though, it allows me to focus and specialize on what I’m awesome at and furgeddaboddit (ahem! delegate) the stuff that I suck at to those who excel at those tasks.
programmer_humor
Active
This magazine is from a federated server and may be incomplete. Browse more on the original instance.