skysight-inc/HackerNews huggingface dataset:
This should be your first point to address.

The only thing worse than a junior asking too many questions is a junior not asking questions. Seen many times people taking pride over quality and spend weeks in their own hole coming out in the other end delivering completely the wrong thing.

What is being asked? If it’s about processes and system design perhaps there is some architectural documentation, checklists or automation that is missing.

You may also have to realize that learning new tools, on your own, is part of being a swe. You are not in school anymore and will not always be given detailed instructions on a silver plate. Often you have to read tutorials and stack overflow yourself. The seniors should guide you into picking the right tools, best practices and the higher level design. Simpler questions like “how do I iterate a list in react” are things you need to figure out yourself.

If you still have trouble discussing feedback on your work and higher level goals or system design with seniors, it might be time to go look for another opening.
Code that I didn't test fully.
It is very clearly meant in jest. The rest of the article is about breaking down why "according to science" isn't a particularly meaningful term in this case, and by the time the author has reached the conclusion, they are using more rigorous phrasing.
People don't want to die. They'll find a way break out of their houses before starving to death and they'll look for food. It's hard to defend against that at the scale of a city the size of Shanghai. If the government is smart they'll let people out in a controlled way but if I were in Shanghai I won't bet my life on that. Of course it's a matter of timing. If you get out to early you'll be nearly alone and you could fail or worse. If you a too much misplaced trust you die at home.
You’re looking at this all wrong.

Take these experiences and failures as part of your learning. Keep plodding forward and do better next time. If you get a pip so be it. Do the best you can and play the long game. If you have survived 8 months and you feel the passion for what you do you can survive 8 years.
The devil is always in the details. Throughout my career I have learned more from my failures than my successes. I suggest you should also.
Don’t doubt yourself. If you don’t have a learning disability you can learn anything. Just be a bit more careful about the deployments and that really should fall to a devops group. Jr means many things the least of them being your technical awareness. Business acumen, social and many others you are just learning.

Change what you can and don’t try to change what you’ll can’t.

Others have said (and I agree) sounds like your company needs some more robust production processes and documentation practices.

In addition assigning you a mentor would also be good practice ideally someone at the lead level or higher.

Additionally you mentioned your manager is no longer in the picture and that’s critical. Managers are also important in helping to guide you to your technical mentor.

Don’t beat yourself up too much.

Keep marching on.
> The problem is at this point I have been on the team too long to ask any basic questions,

I believe very much that there are no basic questions that are too basic to ask if you don’t know the answer. As an experienced engineer, I go out of my way to ask basic questions constantly so everyone else knows it’s OK, and you wouldn’t believe the number of times doing so has shown that the basic thing isn’t basic at all.

> one of the senior engineers even pointed out they shouldn't be helping me with certain processes at this point.

Just be honest and own that: “I realize that, but when I was learning this the first time I didn’t realize… so now I’m trying to…”

If you’re worried about asking too many questions, one thing I do, which is a variant of rubber duck programming, is just opening a text document and start writing the question with as many details as I know or can find in my iwn already included. This process will certainly involve doing research, but since you’re writing a question and not “coding” other parts of your brain are active and you end up with that new perspective that answers the question for you. If not, you’ll still have a useful question thats well crafted.

I don’t know about anyone else, but I’ll take a junior dev who is curious over one that is cautious any day, but they also need to know when to say they need a second pair of eyes if exploration in some area is or could be dangerous.

One last thing I’ll say, which may not apply to you at all (but it certainly did for me): the more I hid my actual status from people when I was junior the more stress I made for myself and the more stress I made for my manager. Managers want their ram happy and to hit deadlines, and they can’t bring in extra help if they don’t know there’s a problem. Being late with something is, every now and then, just a part of the job, and the sooner that is communicated the better for everyone.
I have been studying different music programming languages for years and eventually landed on the design of Glicol:
https://glicol.org

I think the combo of Overtone and Emacs is really cool. Essentially, Overtone, Tidalcycles, Sonic Pi or FoxDot are note/OSC msg generators for SuperCollider. Perhaps the post should mention that. The reason is that when users start to care about audio synthesis and "sound-based music", then they will find a missing picture/concept between the pattern-based language abstraction to the audio float numbers. My experience is that if a user does not understand this process, it is very hard to master the language, tend to forget the syntax and is prone to errors.

One example is that before I made Glicol, I made QuaverSeries (https://quaverseries.web.app/), which shares a very similar syntax to Glicol. I would call it a functional wrapper for Tone.js. But as a functional programming language, even I myself forget the input/output type for each function after not using it for a while. Yet in Glicol, this problem is solved from the first day as Glicol's node IO are all audio streams. One reason I call Glicol "the next generation computer music" is partly because we are now in an era when browsers can also handle real-time GC-free audio, and audio-first makes a modern design.

In designing Glicol, my experience is that when one begins from the audio level, it does affect the language design a lot. How to make the trade-off among readability, simplicity and ergonomics for speedy writing in live coding performance, error handing, abstraction from audio to language, lowering the learning curve is really an art.
Zim – The Zsh configuration framework
I don’t think the answer to fun will come from the tools, but from the problem.

Programming is not entertainment, but a way to enlarge your brain to solve a difficult problem.

Find a problem that you care about (like you did with the quadratic formula in high school) and program a machine to solve it. Maybe, you’ll be magically 19 again

How did it feel where you wrote that program on your own initiative? If it felt great, you already have an answer
There's an unfortunate issue with software engineering: Perception is Reality.

The technical struggles you've described sound like they're about par for a junior dev. You made some costly mistakes and you think you could achieve some tasks faster? Honestly, I would find it suspicious if a junior dev isn't experiencing those kinds of issues.

However, if you get put on a PIP, it's because someone in your management chain has the perception that you're underperforming. You'll have a lot more context about the political environment -- it's hard to gauge why senior devs might be brushing you off. If they have the perception that you're not achieving up to your expectations, that's going to show up in their own private conversations with your manager (or whomever handles your evaluation). If your manager has a negative perception of you, the healthiest thing to do is to find a different team.

Perception is Reality for your manager if they put you on a PIP or give you a bad performance rating, even if you are performing well within expectations. Perception is Reality for your coworkers when they either do or don't support you as a team mate. Unfortunately, when it comes to imposter syndrome, Perception is Reality once again.

An exercise you can do that will likely help is to look at how others are performing. Actually check to see how much code others are landing, or how many bugs others are fixing, or how many stories others are completing. You might have the perception that you're not performing up to the same level, but you can look at some statistics and get a better idea of what the Truth really is.
Normally when a 2 inch piece of lead changes history, it's a bullet.
> bigger things to worry about

Do you mean things like seeing your photos?

If your 2FA is not stored on the same machine then the attacker won’t be able to log into your bank / brokerage account, and that’s something I consider the main thing to worry about.
Glad you like it! I'll try to tune the difficulty of the game.
Aging is a complex process. Do not ignore something as big and heavy as skin. It is entirely possible that secretions from aged skin cells dysregulate other organs etc. Given that we have been judging a person's health by their skin for centuries, it probably reflects the internal state of the organism somehow.
More places will be added, thank you for the feedback!
what will happen if i logged out incidentally from my server?

with tmux i can just relogin and attach
Depends on type of attack/level of security vs convenience.
Having both username, password and TOTP in you password manager protects against password leaks from cloud services, but not from someone stealing/getting access to the content of your password manager.
Having TOTP on separate device protects against both, but is also a bit more inconvenient in daily use.
thought that way too :-)
Real numbers are defined by properties, usually, and it’s just a “I say these things exist” then.

For example, axioms of real numbers state that increasing bounded sequences have a limit, and it is a real number. It could be that this leads to some contradiction somewhere which we don’t know about.

For example, if you erroneously thought that rational numbers in fact themselves satisfy these axioms, you could construct an increasing sequence whose squares converge to 2, and yet the sequence itself doesn’t converge to a rational (because sqrt(2) is not rational). Perhaps some such contradiction exist for real numbers, and in that respect they could “not exist”. That would mean the axioms are somehow inconsistent.

As the article states, we can construct real numbers with Dedekind cuts that only rely on rationals; I didn’t realise there is any nuance to that definition.
It wasn't for the lack of success. I have no idea how many readers or followers I had, but some of my security related posts made it into more "serious" media and elsewhere.

I think it boiled down to a realization that no one really gave a damn about me, my writing/work/creations/etc. So then, what's the point?

Well, they obviously gave a damn enough to repost your blog to more "serious" media, so presumably some of them did give a damn?

All in all, I think having a blog/github account is part of what a certain subset of IT people 'require' for someone to be considered 'good' - because they also consider its the right thing, and its self-reinforcing taught behaviour. You don't have to listen to that subset, and have stopped listening.

I finally got the feeling back. The one you got when you first started programming. It's wonderful.

And are personally better for it.

Sharing stuff is great until you feel pressured to keep sharing stuff.
Holy shit this comment resonates so much with me. It used to be that you could Google something about your game and find a 150KiB text file article (no ads, no useless pagination/SEO filler) which is a treasure trove of useful information, e.g. https://gamefaqs.gamespot.com/gba/921905-pokemon-emerald-ver... .

Nowadays I'm almost happy if I find at least one sentence of useful information in an entire "article" recommended by Google.

I think the above game example is an example of erosion of both sides: articles have gone to shit, and the amount of care, attention and depth to most games have gone down a lot.
I mean you sort of are describing a sociopath. Lots of murders are motivated by profit.
That people don't understand mathematical induction and it's ramifications.
The author (Katie Arnold) is British. Both names are very normal girl's names in the UK.
Cute. More fun ways to get redirected to harmful links. /s

Appreciate the efforts, though I get real skeptic with link shorteners due to their inherent risky nature.

Are you doing anything to avoid those kind of links in the backend?
Jeder Euro fürs Atom fehlt uns beim echten Ökostrom.

Because if you habe finite resources, you better invest them in something that works than waste a considerable part to do something that probably maybe should work.
> Perl doesn't have a way to say "this value is a number" or "this value is a string".

This isn't really any different than JavaScript or similar languages that perform automatic type coercion. Internally scalars are differentiated. When writing Perl XS (the C extension interface), scalars are clearly differentiated into integers, doubles, strings, references (Perl's equivalent of pointers), and several other internal types. In a sense, a Perl scalar is the same as a "scalar" in many other languages (whether strongly or weakly, statically or dynamically typed), where you have two basic types--scalar and compound types. In C an integer, floating point, and pointer are all scalar values, as distinguished from an array, struct, or union.

So when you do `my $a = 3;`, `$a` at that point is definitely an integer type. However, it can be coerced (both conceptually and literally--in Perl objects are mutable and can have both their value and type changed in-place) into a string according to Perl's extremely complex DWIM type coercion rules.
This problem is unsolvable in the general case.

Generative models will asymptotically approach the same statistical distribution of real data.

Eventually, content farms will make actual websites... and nobody will know the difference.
I think that was an argument in Pinker’s book, The Better Angels of Our Nature. That reading, and especially memoirs and fiction, made violence decline.
On the Kramatorsk train station attack. No, Russia had Tochka U officially in use (and of course we're also able to bring them up from storage, as it does with other old equipment now).
Can you show the source for the serial number?

https://t.me/CITeam/2463 I am linking a report by an inependent Russian citizens driven "Conflict Intelligence Team". This way it may look more credible or less biased in your eyes.

All in all, Russia can't deny these cerimes but makes everything to leave you uncertain and confused. Eventually you stop treating any version or investigate seriously. It seems this strategy works (
This is a tough one. In many ways, programming is just work to get to an ends. Such that if you don't have anything that you are interested in doing with a program, then I question if there is an intrinsic property of the art that will attract you.

Looking back on my starts. Original computer was one you had to type the program from a magazine into in order to play it. Make a mistake transcribing, hunt it down. Get it correct, get to play a game for a short while. Wireframe magazine is recreating this. Each issue has a fun recreation of a classic mechanic.

Moving to a more modern computer, used to be that it was a bit of a programming exercise to keep DOS happy so that you could play different games. If you got fancy, you probably wrote a menu system to pick your games.

Even my first dip into "business style programming" was in getting some gaming going. Friend and I used Access to build a D&D character sheet generator. Got our toes wet with SQL, even.

If you enjoy math, https://projecteuler.net is a good place to see if you can get some programs written that usually explore some fun properties.

Similarly, I remember having a ton of fun coding fractals back in the day. The state of graphics programming is... difficult, though. I'd point back at the pygame zero suggestion, even though I am not a fan of python. :(
not sure if you already read this, but there was a discussion about these bots here a while ago

https://news.ycombinator.com/item?id=28998374
> but it is clear that I am not seen as reliable and definitely not known for completing things fast.

That's what a good company expects from Junior SWE's, what is your manager's expectations? (it should be clear and explicit)

> and I made 2 costly mistake back-to-back that is pushing back the release of a production feature by a while month at this point.

That's what qualified seniors expect from Junior SWE's, where was your team?

> I was sometimes assigned stories no one else on the team had done anything like before, so at times I couldn't even ask the senior devs for help.

Seniors aren't good because they have done specific tasks before. They're good because they're able to adapt their wide past experiences to new unknown ones. Perhaps you don't have a good team?

I generally advise my Juniors that their main job is to 1) Invest deeply in learning, RTFM for everything they touch, do laborious but educational things (eg: read the diffs before vendoring a new version and look at what code will be affected in our current impl). The compounding interest of learning lots early on is worth so much more than learning something late in career.
I will be that guy: Emacs can be used with the GUI and terminal with more or less the same experience.

It is one of many features that makes me stick with it
I put in a moderately specialist topic I'm reasonably expert in. What it wrote was highly convincing. While I wouldn't be particularly impressed, I absolutely couldn't distinguish it from a mediocre human. It's really quite terrifying to think of the internet filling up with this garbage.
How is it possible that npm can be used to build an Android apk? Is npm used to distribute all sorts of software these days, not just js code?
can the US confiscate the oil?
see also https://status.atlassian.com/
Not really sure if you're joking here or not.
>> " one of the senior engineers even pointed out they shouldn't be helping me with certain processes at this point."

Try asking another one lol

Some people don't like to help each other as much as others

if that's a big company, consider looking for other teams/projects to work on

if you're fully remote, try going to the office (and spend some time with your team if they're going too)
> I got my first swe job this past August [...] I have now been on this team for 8 months, and I made 2 costly mistake back-to-back that is pushing back the release of a production feature by a while month at this point.

> I was sometimes assigned stories no one else on the team had done anything like before, so at times I couldn't even ask the senior devs for help.

> my manager has been gone since December

> I have been on the team too long to ask any basic questions, one of the senior engineers even pointed out they shouldn't be helping me with certain processes at this point.

To summarize: you have no prior work experience, you're assigned tickets beyond your abilities, management is MIA, your team doesn't support you, and people make you feel bad for trying to improve.

It's not you, friend.

As a junior engineer, a lot of responsibility falls on your environment to help you grow and gain more independence in your day-to-day problem solving. Your environment is demonstrably not living up to that obligation, and they should not have signed themselves up for it if they weren't prepared for it.

I've been on teams that have been similarly inhospitable to juniors. Several of us went out of our way to provide that support, because it's necessary. But nobody higher up had planned for that need, so our schedule was impacted anyway.

It's not you. Try to look for other teams (possibly within your current company!) that are willing and able to nurture your growth. Juniors aren't independent; that's almost definitionally the difference between a junior and a senior. Cut yourself some slack, and try to expect more of your working environment.
They aren't murdering anyone though, just writing stories. Almost everyone is motivated by profit, it's not some unique trait of sociopaths.
Which is why I didn't go.

The previous two were cancelled. (There was a "virtual conference" in 2021 which was rather useless. You could watch videos of talks, basically, while paying far too much.
You'd expect that a virtual GDC would be a full 3D environment, but no.)
This year, most of the big companies, including Epic, Sony, and Microsoft, cancelled.
I didn't see much of a trouble in France - yet. It's probably UK because of, you know, that little smart Brexit thing.
So this is not a joke?
> Not to sound too harsh but if you made the exact same mistake twice (or more!) it's on you.

This. The first mistake in a class of mistakes is a freebie, and even if the outcome was pretty bad, if it was also a process failure, it's not on you. After that you should know better. Too many different mistakes is also bad because it shows you're not being careful.

Think about how actions might be risky. If the process is error-prone, triple check your work. If you're not sure if something is right, ask. There will be situations without guardrails, and you need to learn how to work without them.
>This isn't really any different than JavaScript or similar languages that perform automatic type coercion.

"1" + "1" is "11" in JavaScript. In Perl, it's 2. There's also no JS-like `typeof` operator in Perl. The types you mention in Perl XS are just an implementation detail from the perspective of the language itself. "1" and 1 are exactly the same value, not different values that can be coerced into each other.
Ruby and ruby on rails is really fun.
My seven year old would say: O...M...G.
You sound like the Dropbox guy. Sure for someone with experience like you it may be simple to set this up and maybe even faster, but some of us want to focus on our core product and not worry about this sort of thing. Knowing there's a provider I can call when something goes wrong with file uploads can be a big peace of mind.
you approximately just described adversarial networks (GANs). One of their training metrics is that it is how difficult it is for the "other" network (the adversary) to train itself to distinguish the real from generated.
Chernihiv: Are these Russia's weapons of war?
I am in the exact same category as OP , and there are options. Yes they are annoying. But so is Indian politics and bureaucracy. I view them as equally annoying.
Can’t you back a joke? ;)
Its not too unfathomable. Indigenous people are around today and they pass on lore to their youth the same way. Also looks like they use paint to make drawings. Probably recorded some of their history too.
I learned digital print design because I saw the world of pen & ink design get flattened by computers. I learned web design because I saw digital print design get steamrolled by the internet. I decided then to learn programming as self-defense. I'd had two careers rugpulled on me by age 20 and I didn't want to have that happen to me again. Of course it still happened a few more times but that's another story for another day.

I had a decent career in programming, but over the last ten years or so I realized that I didn't really enjoy it. I was OK enough at it, but being around world-class people convinced me that I was only ever going to be OK, and that wasn't enough. What I really do enjoy is solving problems, and more importantly, finding the right problems to solve.

What rekindled my interest was working with my kid. It's cliche, but games programming with kids is hella fun because it's personal and low-stakes. Minecraft mods, scratch apps, etc.