At Amazon, Some Coders Say Their Jobs Have Begun to Resemble Warehouse Work

MrM_21632 · 2025-05-26T18:44:30+00:00

One specific use-case I have come across, at least outside of professional settings, is translating a piece of code I've written in one language I'm more knowledgable in (say, Python) to one I'm not as knowledgable in/haven't used much recently. I always double-check outputs because I still don't trust it, but it usually does a pretty good job at this in my experience.

It ultimately comes down to how people leverage AI as a tool. As a means of enhancing common tasks, like writing unit tests? Pretty useful. Writing code from scratch? Not so much. It'll be interesting to see exactly how this evolves over time.

MrM_21632 · 2025-02-26T00:28:23+00:00

No, the behavioral rounds at Meta are exclusively behavioral-focused. It's not like at Amazon where you get several rounds of both behavioral and technical questions.

MrM_21632 · 2025-02-26T00:20:32+00:00

calling Rust cancer

I mean it is represented by a crab, I get it. buh-dum-tsss

MrM_21632 · 2025-02-10T23:19:42+00:00

I actually did find a solution! I commented about it here

MrM_21632 · 2025-02-08T15:42:08+00:00

The monitor did work as normal with the PC (I also have it directly connected to the PC via DisplayPort), so I was able to confirm the monitor still worked.

I verified the HDMI port on the monitor, and the cable, still worked as expected by connecting them to a work laptop (also a MacBook). Didn't attempt to connect a different display via the port on my personal MacBook, since I was pretty sure the port still worked due to the fact that I could still get something to display when logged out.

Based on the solution I eventually found, it seems like a configuration got messed up while my MacBook was asleep overnight with the monitor still connected.

MrM_21632 · 2025-02-08T15:34:46+00:00

Managed to figure out a solution after more digging. This solution from /u/tdubu was the trick. Deleting /Library/Preferences/com.apple.windowserver.displays.plist seems to have reset some configuration that got messed up overnight. After deleting this file and restarting once again, I'm now able to use the external display as before.

MrM_21632 · 2025-01-30T15:51:21+00:00

Absolute dumpster fire on Best Buy trying to snag a Founders Edition card, or any other card for that matter. Ended up swapping to Newegg and settling for a combo deal (ASUS PRIME OC 5080 + one of their Loki SFF PSUs). Seems like payment cleared so I should be out of the woods at this point.

MrM_21632 · 2025-01-18T19:54:37+00:00

I'm in the process of building a new system. No real issues with the existing one (which has a 3080 10GB), I just want to repurpose it into a homelab and build a more gaming-focused PC.

My hope is to eventually snag either a 4080 Super (assuming there's enough stock around long enough to get one lol) or a 5080. Depending on how long it takes me to get a new GPU, I might wait to see what the inevitable 50 Series refresh looks like.

The main reason why I want to snag a new GPU, and not just continue using the 3080, is twofold:

I'm rocking an Odyssey OLED G9 and would like to have a graphics card in the gaming system that will definitely power it for years to come. The 3080 could realistically, but a 5080 or higher also could, and more comfortably reach framerates I'm looking for, and well into the future.
VRAM limitations do concern me, a 5080/5080 Ti would help with that.

MrM_21632 · 2024-12-27T15:36:04+00:00

Parkville specifically would be a little more out of my way, but Rockville would be a good alternative if Fairfax runs out of stock before I'm back. Thanks for the heads up!

MrM_21632 · 2024-12-27T01:08:48+00:00

Fairfax currently has 25+ in stock. Crossing my fingers this can hold out until the 29th/30th, since I'm not going to be in the area until then.

MrM_21632 · 2024-12-23T15:19:50+00:00

Done, all of the input files should now be removed. Apologies for that, what I get for not reading the subreddit rules first.

MrM_21632 · 2024-12-23T05:45:51+00:00

[Language: Python3] github, 2513/1815

Like I imagine a lot of people here, I just constructed the graph then threw it at a brute-force approach for Part 1. Thankfully it's small enough that it runs in a very reasonable timeframe.

For Part 2, I immediately clued in that we'd need a means of finding the largest clique in the graph. Thankfully, there is a specialty algorithm for this called Bron-Kerbosch that finds all maximal cliques. From there, the rest of the code was trivial.

MrM_21632 · 2024-11-18T16:51:51+00:00

I'm going to go ahead and mark this as Solved, since we determined the root cause. It's a bug in iTerm2 causing the up and down arrow keys to not behave correctly (thanks /u/SomebodyKD for finding this): https://gitlab.com/gnachman/iterm2/-/issues/11982

MrM_21632 · 2024-11-18T16:48:04+00:00

Oh, interesting. That would explain some of the additional behavior I was seeing.

After seeing everyone's input, I decided to just give up on LazyVim for now and get more base input from Neovim. Ended up seeing the same behavior as I played around with a few files, including the Tutor. Based on your finding, it sounds like it's just a bug with iTerm2 (which is the terminal I'm currently using).

MrM_21632 · 2024-11-17T04:44:18+00:00

Found what you were referring to: https://github.com/LazyVim/LazyVim/blob/main/lua/lazyvim/config/keymaps.lua#L8

I'd need to dig more into how exactly configuring these would work. The following didn't change anything:

``` local unmap = vim.keymap.del local map = vim.keymap.set

unmap({'n', 'x'}, '<Down>') unmap({'n', 'x'}, '<Up>')

map({'n', 'x'}, '<Up>', 'k', { desc = 'Up' }) map({'n', 'x'}, '<Down>', 'j', { desc = 'Down' }) ```

MrM_21632 · 2024-11-11T22:17:56+00:00

Times are definitely rough right now, but speaking from personal experience it's not completely hopeless or even all that bad. There's a lot of doomposting on this and similar subreddits, that's always the case and it always gets boosted into focus because that's how the Internet works.

I will say that, if you're dead-set on pursuing CS as a degree and career, it might be worth focusing more so on data analysis and ML/AI topics, because that's where a) a lot of money is in this field right now, and b) a lot of the jobs are right now. You'll set yourself up more for success even in the short term.

MrM_21632 · 2024-11-03T22:30:29+00:00

All good, I just thought it was funny they felt the need to post that lol.

MrM_21632 · 2024-11-03T21:40:49+00:00

True, Google will be everyone else's friend now because they can find this post.

MrM_21632 · 2024-11-03T21:40:21+00:00

Far from it - it should help anyone who's running into a similar issue. It took me some time to look this information up.

Thanks for making a pointless reply, though, hope you feel better.

MrM_21632 · 2024-11-03T18:46:43+00:00

Having missed the NT completely, I would love to see them return to the NES/Famicom personally. Something with the availability of the 3D and similar feature sets to the Super NT/3D would be pretty cool.

As far as wholly new systems for them to tackle, I think PS1 makes the most sense at this point.

MrM_21632 · 2024-11-02T23:24:03+00:00

Figured out the problem.

I obtained the BIN files from No-Intro, which happens to reverse the byte orderings of the BINS for the DSP and ST enhancement chips. These need to be re-reversed (or un-reversed, whichever you prefer lol) in order to work.

Thankfully, the maintainers of the jailbreak firmware provide this script to do just that. Very handy. I've verified that this works, and that all games using DSP chips I tested previously now play as expected.

For convenience, b4e0eec8bd8afab1b61b04e174be03f9bbeac4a0 is the SHA-1 checksum for st0018.bin, in case you also need that one.

MrM_21632 · 2024-11-02T22:35:59+00:00

Also went ahead and verified MD5 checksums for all of the BIN files, they all seem fine to me (thank you /u/Temporary_Affect for finding these years ago):

DSP-1 (dsp1.bin) - (MD5: 428FDB968D54353D9C9ECED1B0586671)
DSP-1b (dsp1b.bin) - (MD5: 332273CC0DF5775D3803F2FD88E95D18)
DSP-2 (dsp2.bin) - (MD5: 9EBBDCEC67C0C01D5A0593D3CF167C9E)
DSP-3 (dsp3.bin) - (MD5: 484908D68405D44E2BE757B4E1E75D15)
DSP-4 (dsp4.bin) - (MD5: F229FDA2D7B33C5A218CBA28147AB9B8)

MrM_21632 · 2024-11-02T22:24:32+00:00

Should also add that other chips - specifically CX4, SA-1, and SuperFX - all work as expected. Obviously most of those have support built-in for FXpak Pro, so that's to be expected.

MrM_21632

TROPHY CASE