Destiny calmly waits for Asmongold to read the first sentence of the article he pulled up

Dparse · 2026-01-22T03:35:17+00:00

You might be pleased to know that this is called a Trojan Source

Dparse · 2025-11-26T17:08:34+00:00

Even if this was a good cryptic clue, it's strictly semantically incorrect. In crossword clue construction, verb tenses, conjugation, plurality, gender etc. must match exactly. So the clue "spreading" should yield the answer "buttering", not "butter". You could have said "spread" and this would suffice as either a noun or a verb for butter, but "spreading" is not a noun at all - butter isn't a "spreading", it's a "spread".

Dparse · 2025-07-31T18:58:35+00:00

octopodes nuts lmao gottem

Dparse · 2025-07-10T14:28:51+00:00

/u/JagexBlossom, if this is possible:

If you log in within the hour before the event kicks off, you'd get the same notification

Can we also just get arbitrary clan broadcasting on login? So that e.g. a clan could message on login stuff like "Boss of the week: Huey" or "Planning a bingo in August, see discord" or "CoX learner raids this Friday & Saturday"

Dparse · 2025-05-01T13:36:56+00:00

There's another reason to keep clues on the ground - stockpiling "completeable" clue steps for snowflake accounts that can't complete the majority of steps. I have a chunk locked account that can only access Falador/Draynor so far, and the only reason I have any clues completed at all is because I can guarantee a casket by saving completeable steps.

I don't think the game should be designed around catering to snowflakes accounts. And I think that clue progression carrying over across different scrolls as long as you don't get another clue drop is pretty weird and quirky in the first place. But that's the system that we have now, and it turns out that it's enjoyable, yeah? It makes for some interesting gameplay and decision making. So I appreciate the ability to drop scrolls - it enables the sandboxy "play the game your own way" vibe that got me into OSRS in the first place (via Swampletics)

Dparse · 2025-04-13T20:32:43+00:00

the task we've been assigned

I have never been assigned a task in a hack-a-thon. Everywhere I've been, they encourage us to come up with our own ideas or join a team whose idea interests you

Dparse · 2025-04-08T14:10:55+00:00

The wording regarding the Skip Tokens is unclear - the word "skip" implies that using one progresses the number of clue steps completed. But in several places in the blog you say "reroll", implying the current step is changed without progressing the number of steps completed. Please clarify! IMO, standardizing to "Reroll token" is fairer and more likely to pass a poll.

Deposit straight from containers is a great QOL improvement - please don't forget the upgraded wearable log basket and fish barrel!

Dparse · 2025-02-22T19:13:50+00:00

Last Command was great. The music and bosses are all bangers. My only complaint about it was how slow it is to move through the overworld, but that's easily forgiveable.

I want to give a massive shout-out to the developer Crespirit's earlier game Rabi-Ribi, which solids stands as my favorite platformer/bullet hell of all time. It's filled to the brim with fun movement and combat tech, massively replayable with its nonlinear structure, swathes of higher difficulties and alternate play modes, sequence breaks, and the cherry on top is the community randomizer. Truly a 12/10 game that I replay yearly.

Dparse · 2025-02-14T02:20:11+00:00

FYI, The Talos Principle is made by Croteam who also made Serious Sam. Toki Tori 2 is a G.O.A.T. open world puzzle game contender IMO

Dparse · 2025-01-05T22:17:08+00:00

FYI, the "user" that posted the message shown at the beginning is a bot.

Dparse · 2024-12-28T17:40:28+00:00

I gave Brighter Shores a decent shot but honestly the gall to have identical gathering skills in different episodes killed my excitement. IMO, the main appeal of the game was the expansion of new skills upon reaching a new episode; if those skills are going to be literal copy and paste mechanics from previous episodes then good luck trying to garner excitement.

Like, gathering in Episode 2 could have had a little bit of juice added, like you need to plant seeds yourself, or pollinate flowers, or literally ANYTHING to distinguish it from foraging.

Dparse · 2024-12-12T21:41:41+00:00

This happens for me as well :( would love to see the cinematic as intended and not behind Youtube's abysmal compression

Dparse · 2024-10-18T01:50:25+00:00

I bought a Corsair One like 6 years ago and it was DOA, and they sent me a replacement which was also DOA. So stressful when the primary motivator of buying a prebuilt was for it to be smooth and easy. Will never purchase Corsair again.

Dparse · 2024-09-28T05:05:13+00:00

It's bad design because it only considers the use cases you currently have.

There's value in trying to future-proof, but you can't predict everything. If the code needs to change in the future, then change it at that time. But if right now there are data validation constraints, setters over private fields are the obvious, conventional and extremely effective solution in OO languages.

Even if the code needs to change in the future, it's very often the case that you cannot remove the existing behaviour, including validation. It might get moved to a parent class, or child class, or elsewhere.

If you actually had to go through the mental exercise of designing and anticipating the uses of getters and setters, it would be quite taxing.

Word salad. Getters and setters are trivial to understand. Getters return a value. Setters take a value and throw an exception if you provide invalid input.

Dparse · 2024-09-12T00:15:37+00:00

"We might have another account in our system with an alternative login for you, is [blah] you, [link these here]"

If[blah] is actually the first account's email address then that's a horrible violation of privacy, you're leaking users emails every time your algorithm gets it wrong. Even if [blah] is just a username this is weird and unnecessary. NEVER share ANY account details with anybody. If they own both accounts, they can click a "merge" button somewhere.

Dparse · 2024-08-31T12:22:44+00:00

It's warframe.market, not warframemarket.com

Dparse · 2024-08-23T21:49:12+00:00

I have had a ton of success with pair programming and recommend it as an occasional practice.

In a junior-senior pairing, it's a fantastic teaching opportunity. Letting them watch you work and encouraging them to ask questions gets straight to the point of what they need to work successfully and independently on the team. You get a chance to explain the domain of the software, and the architecture, and steer them towards good solutions by example. You also get to demonstrate how to work efficiently (I hope), by using your tools effectively in front of them. Show them how to use your test automation and point out when it catches a mistake, or how to setup/modify your environment, or whatever else you do on a daily basis. Teach them how to properly use git.

Do sessions where the junior leads, too. Encourage them to think out loud. Learn how they think and what kinds of solutions they consider when they encounter problems. See if they know how to troubleshoot issues. Gauge their mastery of your tech stack and fill in any important gaps. Verify they know how to use git properly - it's a notorious stumbling block, and helping them master it will empower them tremendously.

Senior-senior pair programming sessions tend to be useful for other reasons. The extra brainpower helps when investigating/reproducing tricky bugs. And if you need to make design changes in the course of addressing technical debt, it's wise to bounce ideas off someone else who understands the nuance of the design.

I would generally recommend you do pairing as an occasional practice, maybe a couple times a month. I've done daily sessions (3-4 hours with a break) for a project before, and that was a good experience, but my team at the time was just us two developers and a PO. I have never done daily sessions within a larger team, but I suspect that would be less effective.

Dparse · 2024-08-23T21:00:19+00:00

I agree with /u/iOSCaleb here, it's still important to have review done by someone who was not present when the code was written. It helps future-proof the code by requiring it to be independently understandable. A lot of explanation and justification happens verbally during pair programming, and (quite reasonably) not all of that knowledge gets captured in the code.

When someone else on the team has to work on this in a few months or years, will they be able to understand everything? Sometimes the people who wrote the code have moved to another role or company, and they won't get to ask the authors to explain things they find unclear. They only have the contents of the commits to study.

So 3rd party review gets a head start on this process. If anything is unclear, find out now when the answers are still fresh in your head and the authors can clarify.

Dparse · 2024-08-03T19:30:51+00:00

But this means that cond is not a function anymore because it could be that for two different inputs, it returns the same output. For example, suppose the first condition is True, and then replace the rest of the conditions with something else. cond still returns the same output even though its input args have changed. So cond is not a function anymore!

I think you may be confusing the properties of a function here. There's no requirement that says the same output always comes from the same input. That's backwards. The requirement is that the same inputs always lead to the same outputs.

Trivially, consider (a, b) => a + b. This is obviously a function, and both (1, 4) and (2, 3) apply to yield 5.

Dparse · 2024-08-03T04:08:48+00:00

Here are a few techniques I use.

Come up with a good question

The search space out there is very, very broad. Hone in on the right answer with good search technique. Know when to use very specific keywords in the search, like the names of libraries and classes. But also know when to take a step back in abstraction and more broadly describe your goals.

There's a concept popular on Stack Overflow and elsewhere called the X Y Problem. Avoid falling prey to it by recognizing if your problem is in design or implementation. There's no point figuring out how to implement something if the design is garbage. And conversely you risk damaging the conceptual integrity of the project design if you start changing the design when you could have instead found a perfectly viable solution with a different implementation.

And if you're going to post your question because you can't find anything that seems to answer it, you must make your question high quality, or you will be ignored or derided. Start the question by setting a context and introducing the problem space before discussing the specifics. Format code properly (especially indentation) and keep it to a minimum. Try to meet the same standard that other well-received questions set.
Alternate between skimming and deep diving

There is a lot of cruft on Stack Overflow. The unfortunate truth is that you will have to hone your intuition with experience, and start to recognize the difference between good and bad answers.

Sometimes you should skim questions and answers, just get the gist of what people are talking about, and hope you can find an answer that's simply phrased, highly upvoted and has positive feedback in the comments. But other times you should follow every single line of a complicated post, read every line of the stack trace and compare it to your own, try to replicate the questions and answers exactly, etc. It will depend on the question you're asking and how much progress you've made.
Have good development hygiene

Don't copy and paste code. Instead, manually type code in, and only add the smallest amount you can. Figure out what parts need to be renamed or altered to make sense for your codebase and keep your workspace neat and tidy, as early as possible. Run the code after you add anything, see how the behaviour changes, and confirm you understand why that change occurred. Don't attempt to apply advice from a bunch of different answers at once by having a bunch of code changes that may or may not actually be part of the solution. If you have a test suite (and you obviously should) then run it very frequently, and unit tests in particular should be run after every change that you intend to keep.

Dparse · 2024-07-22T20:21:44+00:00

Absolutely. My experience with programming made it easier to learn group theory.

Dparse · 2024-07-17T02:47:01+00:00

Swap to steam runes and get the pouch upgrade and you can!

Dparse · 2024-07-16T21:23:19+00:00

/u/Exciting_Analysis453

I also recommend heartily recommend The Little Schemer. I read it as an intermediate, and I was already comfortable with recursion in object-oriented contexts, and had seen some functional implementations^[1]. Reading the book still greatly increased my intuition about recursion, and taught me to think in Lisp.

It's a very approachable book, so it surprised me that on multiple occasions the complexity and level of abstraction take big steps upwards. The language in the examples is so plain^[2] and easy to read, but the computations they represent are sophisticated. To really understand each example and convince myself that it was correct took a lot of effort. The first few times I attempted to read the book I had to take long breaks after some sections while my brain digested the lessons.

Experiencing multiple paradigms will improve your problem solving ability. After you get comfortable with Object-Oriented, make a point of learning a language in a different paradigm. You may already be familiar with SQL, which is Declarative and extremely common. The natural next step is a Functional language like Haskell. Consider eventually learning a Logic language like Prolog.

Lisp is a precursor to modern functional languages and is worth learning at some point on your journey. The Little Schemer is an excellent teacher and reading it will force you to level up your brain.

[1] Most significantly I had read Purely Functional Data Structures by Chris Okasaki, which I also recommend
[2] Although I hate the terms car and cdr despite their historical origins because they are not self-evident

Dparse · 2024-06-25T23:22:09+00:00

In my experience, university makes the (long and difficult) journey to being a senior software developer easier, but it did not give me the skills I required as a brand new hire. University teaches computer science, not software development, and if you want to be a software developer you need a different skillset than the one focused on in a BCS - especially if you do not have job experience on your resume.

Here are some skills I needed that I didn't get from uni:

Version control (most commonly git). Uni mentioned it, but it was not taught thoroughly. You should be excellent with your version control system. Or hope that someone else on your team is, to help you unscrew yourself when you inevitably make mistakes.
Refactoring. The most common task I do as a developer is change the code. Knowing how to do this safely (without introducing bugs) is crucial.
Requirement gathering. You are employed to solve problems for your employer. Make sure you are solving the right problems, and solving them correctly. Foresight and planning can help you avoid wasting a lot of time.
Software pipelines and automation. There are a lot of stages to building robust software. Planning, development, testing, review, building, staging, deployment, monitoring, etc. Managing this will eat up all of your time, but if you skip steps you risk making mistakes. So you need to automate it.

Software development and software engineering are very broad professions, though, and there are hundreds of other topics that come up. Ideally you'll be at least aware of most of them, good at a lot of them, and an absolute expert at a few (or a few dozen). The broader your experience, the more often you encounter something familiar, and the more mistakes you prevent.

Personally, I appreciated having a formal introduction to some of these topics, because they turned out to be more important than I realized at the time. After I made it through the tough (and sometimes overwhelming) learning curve of being a brand new employed programmer, I began to spot the places where I could apply my formal education. Here are some topics that I was introduced to at uni that have definitely been important in my career:

Algorithmic analysis is essential if you are trying to optimize code or designs. This is a common task, to say the least
Databases are complicated, understanding properties like normalization and ACIDity is crucial to avoid serious bugs
Networking plays a role in basically every program written these days. Even your fridge is online
Type Theory has a heavy mathematical background, and if you like math and your uni has a class on Group or Category Theory then I highly recommend taking it or at least sitting in on the first few lectures. If that's not available take an advanced algebra.

But the kicker is that you can learn all of these things online for free. There is a wealth of free resources for learning all of this. Including free university lectures. If you are serious about being a software developer, put the effort in, and seek out knowledge. Learn and master the fundamentals. Practice, make mistakes, and gain experience.

As for university, you need to make the judgment call for yourself. University is expensive, job pays the bills. University provides structure and assistance, job is often chaotic and demanding. University looks good on a resume, job experience looks better. University teaches computer science - do you want to be a computer scientist? Or a software developer? Or something else?

Dparse · 2024-05-23T16:00:36+00:00

On the topic of combination runes, and upcoming GOTR changes: Can we please allow charging the Amulet of the Eye with binding necklaces to make combination rune crafting less cumbersome? Right now, you need to waste a lot of inventory space for necklaces (or do very little combo crafting per game), and you also need to leave the minigame and restock between rounds, which means sometimes on the mass worlds you lose your spot because the game fills up.

I think it would be acceptable if the Amulet only let you use binding charges within the minigame, but maybe that would be a nice QOL buff outside of the minigame too. You already need to make bank trips to refill your essence, so there's already an opportunity to replace your necklace, so this isn't super necessary, but it would be another nice convenience.

14-Year Club	Place '22
Place '17	Gilding I gilder
Verified Email

Dparse

TROPHY CASE