Hacker Newsnew | past | comments | ask | show | jobs | submit | j-scott's commentslogin

Never mind, I was wrong. Here’s a playground showing how go parses each one: https://go.dev/play/p/hyWPkL_9C5W


> Octals must start with zero and then o/O literals.

No, the o/O is optional (hence in square brackets), only the leading zero is required. All of these are valid octal literals in Go:

0600 (zero six zero zero)

0_600 (zero underscore six zero zero)

0o600 (zero lower-case-letter-o six zero zero)

0O600 (zero upper-case-letter-o six zero zero)


My bad! I was wrong; added a playground demonstration the parsing behavior above.


My original comment was incorrect. These are being parsed as octals, not decimals: https://go.dev/play/p/hyWPkL_9C5W


I work on the container registry team at my current company running a custom container registry service!


How does this require a whole team? Unless you're working at a hyperscaler


Not a hyperscaler, but we’re multi-cloud and probably one to two steps down.

My team’s service implements a number of performance and functionality improvements on top of your typical registry to support the company’s needs.

I can’t say much more than that sadly.


Please describe their system for us, including system throughput, the hardware they're on, networking constraints, and how many people are allowed to be needed to operate it.


Maybe they work for docker


See also Sourcepawn[0], popular in the sourcemod engine community for custom server plugins and game modes.

[0] https://github.com/alliedmodders/sourcepawn


I used this a very long time ago and rather disliked it. My impression at the time was that it was just a worse version of C. As low-level as C, with fewer features, and much slower - unlike a normal scripting language which is slower but higher-level with more features.

They've since changed the language syntax, but this is the version I was dealing with:

https://wiki.alliedmods.net/Introduction_to_SourcePawn_(lega...

No structs/classes/objects. No pointers. You had to store everything with arrays of primitives.


Many hours of fun it was running CounterStrike servers and writing my own plugins. Halcyon days :)


Ah I remember writing a couple TF2 mods in sourcepawn years back. Those were fun to play with friends!


Music production, but I’m finally taking the leap after a decade of saying it wasn’t for me.


I think this was meant as a reply to https://news.ycombinator.com/item?id=43004919


In my most recent cycle, I didn’t ask to use AI and I was only warned once about using AI when I had the official language plugin for an IDE annotate some struct fields with json tags. I explained the plugin functionality and we moved on.

When I was part of interviews on the other side for my former employer, I encountered multiple candidates who appeared to be using AI assistance without notifying the interviewers ahead of time or at all.


Started prepping/interviewing in Oct after reading this post: https://news.ycombinator.com/item?id=41402581

Secured interviews with Facebook, Databricks, Snowflake, and Stripe (3 referrals, 1 recruiter reach out).

Bombed the FB phone screen due to nerves/first interview of the cycle. Completed the remaining three loops by December, and got offers from Databricks and Snowflake (Stripe went on two week holiday break and hasn’t gotten back to me yet).

Accepted the Databricks offer!

Happy to talk about practice/process (within the limits of the interview NDAs)!


Who the fuck is making you sign NDAs just to interview? That seems absurd for most roles/places.


Databricks, Snowflake and Stripe required NDAs for the onsite portion of the loop.

The NDAs covered anything internal discussed during the hiring loop.


That's crazy. Unless they're hiring you to solve a novel problem there's really no reason. If you're not paying me for the interview, I'm not signing an NDA.


From the interviewing side -- if you're under NDA I feel more free to answer arbitrary questions about the business. But your opinion is not unique, so my current company stopped asking for NDAs. We sometimes still do it during the offer stage if a candidate has a lot of detailed business questions


Yeah, I could totally see it being valid if I start asking for business model or implementation details. The only time I thinknid ask something that detailed would be if it's a startup and I want to understand their financial situation to see if they're stable.


If you're interviewing for staff level positions and above, you'll be discussing long term planning and some pretty tactical stuff where an NDA makes perfect sense. Might be a bit overkill for senior and below but meh.


Yeah, I could see it for any sort of high level position. I wasn't thinking in that context. I was thinking for just regular devs.


Are they all in-person now or remote? Also wondering how you secure interviews with the big tech companies if you don't have referrals per se; I do have friends at some of these places but I've mostly worked at smaller companies my whole career, and some contract positions at bigger Fortune 500s, I'm not sure if big tech would go for my sort of profile over others who've worked at bigger companies or other big tech companies.


Are you in the Bay Area? Do you know if Meta requires all employees to commute to their S. Bay campus?

I have a recruiter pestering me from them. I'm open to Meta but not commuting. If their SF office is open though I'd consider an on-site role.


Not in the Bay Area, but I have friends at FB and I believe their RTO policy is strongly enforced unless you’re senior and have been at the company for a year at which point you can go remote.


Is the meta interview process still primarily a leetcode gauntlet?


Phone screen was 2 problems in 45 minutes, I believe the onsite portion would have been more of the same but I didn’t get that far :D


Sounds like yes then. I thought they would have stopped doing this after the layoffs bc they hired too many underqualified people with that method.


This is very similar to an issue I had while playing games on a wired Windows desktop. I haven’t run into it in a long time now that I think about it. I wonder what might have changed.


> People who stress over code style, linting rules, or other minutia are insane weirdos

Stressing over these things is certainly a Sisyphean task.

However, investing in automating and standardizing the application of these things every time a new repo is created eliminates an entire class of problems and saves you all sorts of trouble down the road.


I am one of those weirdos that like to work on "un-sexy" things behind the scenes which hopefully makes the life of my colleagues a bit better with every attempt. I don't think it is necessary for small teams, and may even be considered a waste of time, but once a team is sufficiently big and spread out, I think a few people working in the background, keeping watch of things, cleaning up after people, proactively improving stuff, creating and enforcing rules and standards is very beneficial and necessary for a team's next growth spurt.


Everyone uses the same formatter & options (which really should have no options, but that ins't the reality for most languages). The formatter rules - move on.


Primarily it's protecting yourself from those weirdos by pre-empting them, though.


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: