argentum47

Nice, but I guess you would need to talk a lot of guys to get product integration. Will this also make hardware? like PCB design? That stuff is quite difficult to get right - with all the impedance and resistance and capacitance acting together.

A friend of mine sent it to me and it seems like an interesting option now that hardware pricing has gone insane?

Self hostable at https://github.com/go-batteries/shortner

A few years ago, had worked on a db resolver for gorm v1. This is an extension of it, decoupling gorm and adding request coalescing.

This opinion might be a bit controversial, so correct me if I am wrong.

Going by the Think Fast Think Slow, most of the people who were great at what they did, could be categorized overall, in terms of how they put in their effort, where they put in, and when they started from. (Apart from luck)

I think of this in terms of traits. Big tech companies, they would want to avoid any form of engineering silos, giving so much power to a single/single set of engineers, that would halt their business. Which is why they have this process.

They want a whole lot of easily replaceable engineers, who (might work on different projects), but overall have the same kind of mentality. This way they know, if the candidates have done what they need to do, and talked about things a certain way, they on a fundamental level would be the same. So even if the person leaves, the style of work for the next incoming engineer wouldn't change, and everyone can go along with minimum friction.

Also, thinking a bit more, /^[FAANG]*/ companies would obviously try to cross-hire. Same as BIG4, same as /TCS,CTS,Infosys/ and likes. A good chunk of people who work in MNC's stay in MNC's. Infact sometimes the projects are transferred from one MNC to the other, and then the manager or TL or whatever leading the project is hired first, and then he/she brings his/her team from the previous org.

Although end of the day, there will be a few hits and misses, but given the plethora of people working there, on a large scale of things, it doesn't really matter. I mean in a group of 20 people, 2 leaves. Its barely anything to make a dent.

> Let us know if you’ve seen the problem previously.

It was one thing to practice this for hours, and now I have to tell them, yeah I saw this problem, so given me something that I never solved, and have a 50-50 chance of win.

So working at Meta would be like, oh we need an Auth layer, but we have already seen an Auth layer being used, So lets scrape that, and build a new one, but then we are not going to look the spec or the problems from before, because we want to do the same things again.

Now you can do this as well.

https://drcsv.onrender.com/?url=https://raw.githubuserconten...

Add the publicly available csv file to the URL for quick filter and search and stuff

toned down the blue

I did a black one. I will experiment with the blue one. After looking at the bllue for sometime, when I look outside, I see different colors :D

Added the black stuff, more reference images would be awesome.

I have to check once. I haven't worked with C++ builder

I think what I am gonna do is, make this a central repo, and support more of these old school themes. I am gonna take the feedbacks down here and see what i can do.

I will crater to your wishes.

Repo: https://github.com/ikouchiha47/drcsv

This is a proposal for an extended ISO date format. From the pains of my previous work experience, I saw, all other parts of the dates were quite unambigious, but when it came to month and date, the information is lost. There has to be some understood contract between parties to adhere to the formats. This is unnecessary. This date doesn't need to be widely used, but for b2b maybe, where we have to parse date from different vendors. Mostly none of the date formats deal with this. There is no way to tell 2016-01-02 is YYYY-MM-DD or YYYY-DD-MM

P.S. I took the help of GPT to fix the english in the draft.

ok, thanks for suggesting, didn't know this. :)