qualsiasi

I'd love to begin the year with a book on Rust and another one on being a team manager/lead because I got promoted as a lead (a team of 8) but I totally feel I'm unprepared.

I would love to do so, but we're always in a hurry for this or that project. I can't tell how many times I reported to the management that this way we're worsening our codebase and piling up technical debt. But revenue is revenue, and they always tell me "next year"... this is true also for education. I've been here for five years and attended only a mandatory course on workplace safety :)

In my company (medium size, 400 people or so and 300+ devs) code reviews are unheard of, everyone commits to the trunk. And I think this is the case in most companies.

I'm not happy, not even a bit, with this. But it's the status quo.

Our customer only uses IE11, so this won't affect my work

I have only one experience to share. Interviewers (2) asked me to choose my favorite time to be phone-interviewed in a window of 4 hours, 9-13, more like 9-12.30 because by 13 call had to be completed.

I took 1 hour off from work to attend, then the "conf room" wasn't working (conferencing pin code was wrong). This made them re-schedule the call. Then they asked me to re-schedule again. Then again.

Finally we arranged for a given time and day, with a working conf room. When I called-in they were interviewing another developer on the same conference room. And it wasn't the previous interview... they actually scheduled two interviews at same time because they messed up with time zones.

They canceled or rescheduled interviews giving note no more than 30 minutes before the agreed time. So in all this I lost 4 hours of work. At the end I gave up and withdraw my application, not worth it.

Wrote a mail address in source code thinking that no developer ever would test the app configuring a real smtp server.

We ended up sending emails to the board of a multi-billion company containing "bad words" as the dev were filling text fields with insults and whatever during their tests. I didn't get fired but I still think I was very close.

It's not different at all, but you might not want to add this "breaking" scenario to any component in your app, or you might accept the risk - up to you.

If you accept the risk for any component to break you'll eventually end-up spending your time fixing something other people broke, offering a poor experience to your end customer.

Mind that in corporate environments getting authorized as a software supplier to deploy an update could take weeks if not months, in the meanwhile the customer perspective is that "your product broke" (and made them lose money) - this is why I like to ship as many dependencies as possible in the final bundle.

This is my opinion, maybe biased by the market sector I'm working in. Not saying it should work the same way for everyone, just my 2c.

I am not a lawyer but checking out some sources it looks like you’re not allowed to do that. Relevant law should be law 110/75 article 4.

> should

What if a bug in Chrome (layout rendering, dom, ..) breaks your application? It's a corner case, possibly it will never happen. But this solution makes impossible for you to roll out a patch by just changing Chrome version bundled.

User will notice a bug in your application and maybe none of his frequently visited web-apps/web-sites exhibits the same bug, so you won't have the user engaged to update (or downgrade!) his Chrome version.

All in all you're breaking one thumb rule which is to use fixed versions of dependencies for your products, so to be sure they always work as intended. As a side note, how is one going to test a GUI build this way? Should it be tested against all Chrome versions that may be possibly installed at least at one customers premises?

In my country (Italy) AFAIK you're not allowed to carry a knife (any size, even the smallest) in any public place (pub, restaurant, post office, ..). Even on the streets or driving the law enforcement officers could ask you for a sound motivation to carry it.

I'd go with the matematician, Cardano. > https://en.wikipedia.org/wiki/Gerolamo_Cardano

I would be curious to know what would be the elapsed time on the same machine (and problem) using more "enterprisey" languages like Java, C#, ...

Python is really widespread, but at least in my company it's used for analysis and prototyping only. Then the prototype is ported either to Java, C# or C++.

I don't know if it's common practice, but we work like that and totally makes sense to us.

I'm no expert, but wouldn't be more efficient to completely replace the BMC with a malicious one? That way it should be virtually impossible to detect

If someone would ship this to our office with a note like "attach this to a LAN port" chances are it will get attached. And we're a software house. People tend to pay attention to viruses, etc.. but not physical security.

Somethimes you just use a few branches for testing feasibility - most of the time at my current company this involves zero testing and poor code quality. Moreover some developers (me included) are afraid of losing work and push frequently even "broken" code just for the safety of it. I tend to see feature branches as a "work in progress" and as such code quality could be temporarily lower than expected. On merge request linting and testing should however be good.

Could you please tell us how you got that job? I'm constantly on the look for a full-remote job, but I find difficult to get one.

On all branches it seems to much to me, but maybe on master (or any release or pre-release branch) you may want them.

At my current company we're on such an old and badly written codebase that this kind of hook would just annoy 90% of people. In fact some years ago we tried to introduce that and people escalated quickly to a manager and had that removed.

I always wondered how you can submit your work for approval and publishing from outside the academic life. Are there conferences that accept submissions from someone who is totally unknown?

I honestly thought that average was 60/80k