If one is unable to work alone but manages to join a new company with an inflated title, people will notice. They're gonna have to keep job-hopping until they find a place that doesn't notice the bad performance anymore.
This is demonstrable by the amount of CVs with "12 jobs in the last 6 years" in my reject pile.
That's an old ASP.NET Web Forms / ASPX thing that was IIS-based. IIS would just compile .cs files into a temporary folder when first running. So the first request takes like 5s or something.
It's not the new .NET Core AOT feature, GP was building the DLLs and packaging the website locally.
Not GP but funny enough I ran into a similar problem with a team that also didn't know compilation and was just copy/pasting into a server.
>> So the first request takes like 5s or something.
I haven't worked with IIS in more than five years, but couldn't you change some setting to infinity so the thread never sleeps... or something like that? I remember the "5 second" thing being a problem with commercial IIS apps we deployed, and that's always how we avoided it.
This "pause" would only happen for the first request after uploading fresh source code. This is not like Heroku or AWS Lambda. The compilation results were stored in a temporary folder, so you could restart the server and you wouldn't see the issue.
The solution was just to compile the app before deploying, as grandparent did.
Even back then the general consensus was that "not compiling" was a bad idea.
This feature dated back to the .NET 1.1 days and was a " web site" project vs a "web app" project. It operated much like PBP, in the sense you could ftp raw code and it just worked, but it could also just blow up in your face because the whole site was never compiled in one go.
If you have PMs answering the how of issues such as "we need to improve performance" or "we should probably think about scaling", then the senior engineer on the team is the PM, not you.
The list of example questions at the bottom is clearly not exhaustive.
Sure, those two specifically can be handed off because they involve basically no user journeys for the product and a PM can't reasonably be expected to know the technical details of performance or scaling. But any PM or engineer should be able to at least ask "is the performance bad everywhere, or only specific things"?
But a PM absolutely should be diving deeper to get more details on "users are complaining about the onboarding flow" and figuring out what should be fixed or what the ideal onboarding flow should be before involving an engineer. The exception of course is the onboarding flow has errors or is slow, which again the PM is not responsible for.
Assuming that a PM should ask/answer everything before handing over to engineers is possibly the #1 reason engineers never progress beyond the junior level.
We're not in 1980 anymore. Most people need zero, and even power users need at most one or two apps that need that full access to the disk.
In macOS, for example, the sandbox and the file dialog already allow opening any file, bundle or folder on the disk. I haven't really come across any app that does better browsing than this dialog, but if there's any, it should be a special case. Funny enough, WhatsApp on iOS is an app that reimplements the photo browser, as a dark pattern to force users to either give full permission to photos or suffer.
The only time where the OS file dialog becomes limited is when a file is actually "multiple files". Which is 1) solvable by bundles or folders and 2) a symptom of developers not giving a shit about usability.
I remember trying to use music I had bought in a slideshow that year and finding out that I couldn’t load tracks with DRM into the editor I was using; it was very frustrating.
If the source and target are both lossless, then yes. ALAC was available in iTunes since 2004 AFAIK.
Caveat: CDs were 44.1/16 so if the original files had more bit depth, they would require downsampling. Technically lossy, but not "compression" per se. But AFAIK, iTunes was also 44.1/16.
I recently had a terrible experience with a developer who only communicates this way, and it's terrible.
Every single sentence is way too complicated, vague, deferring, or hand-wavy, and I can't know if they're being honest or just bullshitting me.
Half of the terms are incorrectly or are exaggerations when I probe: "Coupled" means "the code is confusing to me". "Monolith" means "the architecture is complicated to me". "Refactoring" means "adjusting the style". "We need a new abstraction" means "we need a new idea".
The team already had some issues with misunderstandings because of the above.
It's someone so eager to be part of the "big boys club" and trying to push their way to the top.
Apocryphal, but someone once told me history of male grooming is an example of this: When only rich people could afford to shave, the fashion among the noble was to have a clean-shaved face to signal status, and poor people had beards. Once safety razors appeared, then the trend reverted.
If one is unable to work alone but manages to join a new company with an inflated title, people will notice. They're gonna have to keep job-hopping until they find a place that doesn't notice the bad performance anymore.
This is demonstrable by the amount of CVs with "12 jobs in the last 6 years" in my reject pile.
reply