If you stay late it looks like a) you're struggling, b) you're a try-hard, c) you don't have a life after work.
One of the most actionable low-hanging career advices I could give is be among the first ones to pack up and leave for the day. You can always continue working at home if you're not done.
When I worked for a crypto startup early in my career, we were once chastised because no one was in the office at 6:30pm. Some engineers (including me) did mostly work from home but most people, engineers and non engineers alike, mostly worked from the office.
And a couple years ago I did a short consulting stint for an AI startup (I know how to pick the bubbles huh?) where I shipped something at around 6pm my time, got a call at 9pm their time to talk about it, and then he asked me "what are you working on tonight?" I quit the next day.
Anyway, this advice confuses me because many companies see staying late as a badge of commitment. Maybe it doesn't apply to startups.
Don't ask me. It wasnt 200k it was like 170 something. I can't say too much but it was some big weird ETL pipeline using some weird database. Tons of weird algorithms for displaying data, by storing it all in memory? I don't know man I wasn't allowed to talk to whoever had swarms of agents create it. From what I understand of it it was a complete hazard
Linux kernel has I think tens of millions of lines of code for reference.
I don’t understand what the downside of this is. That’s hilarious for them to expect, and you’re free to ignore them, take their suggestion and work on it, help them.
With hindsight, it's always easy to say anyone could have done it too, but there's more to product success than just coding and shipping an app out the door.
The first iPhone was built using COTS(commercial off the shelf) parts that Nokia, Ericsson and Motorola also had access to, and SW tools they also had access to, yet Apple won and buried the other companies because their end-product was way more popular with the customer base. I'm sure engineers from Nokia, Ericsson and Motorola also said "we could have done exactly the same thing with the right leadership" when they saw that.
I also say "I could have done that" when I see how the maker of Flappy Bird became a multi millionaire, or how any other top 100 AppStore slop app has 100+ million downloads.
Coding skills are dime a dozen these days. A lot of people can do 95% of these things now. The differentiator between failure and success, comes with the 5% rest: network effects, market know-how, promotion, timing, outreach, UI, UX, luck, etc.
I agree it was a good idea and there’s more to product success, but you were specifically talking about coding skill level.
There are some things I could easily say I (and many others) could not build even in retrospect. Solidworks, for example is beyond a lot of people’s skill level and very difficult to build.
It's a book that is much more interested in presenting an almanac-esque survey of everything that was happening in cryptography at the time it was written (also unhelpful: it was written at a particularly un-rigorous point in the evolution of cryptography) than it is in teaching readers how to accomplish anything safely.
I have never heard this said before. I wonder how true it is in general
reply