I've always thought that the preparedness of employees to boot seniors out of their booked meeting rooms was a bellwether of good corporate culture. Places that values everyone's time and leaders follow process by example.
The Volte | Senior Software Engineer | Remote (must be Australia, NZ, or UK resident) | Full-time
Help us to scale our P2P fashion rental marketplace, enabling people to enjoy the clothes they want, but more affordably and sustainably than by filling their closets.
Work will be a mix of data and platform engineering + feature related tasks. The right candidate will enjoy a high level of autonomy to optimise and innovate with our modern web stack (Elastic, Django, GraphQL, React / Next.js).
Enjoy working in a fun and growing industry. We promote a culture focused on learning together, whilst building features our customers love to use.
If management discover that you knew about the wastage, and did nothing, then it can be said that you aren't acting in the best interest of the company. Possibly the opposite, meaning you'd be fired. So there's that.
If there is a culture of apathy and zero oversight and you are 100% sure no will ever care to show that you knew about it, then I pity your situation. Not bothering to tell someone about the wastage it is perpetuating that culture. Eventually company will fail or at best struggle.
I'm my experience it's nicer working at profitable companies where everyone is doing their best to help the company to profit. That doesn't mean your income is less important than company income. But you agree on the former, then do everything in your capability to help with the latter.
If your still not convinced please consider the environment. Cloud services consume not insignificant physical resources.
I love Django but think this is a pretty sensible stack for a single developer who is strong at JS.
You are still going to have to make a lot of correct library decisions to implement key features like auth and a DAL. Nest JS is an interesting batteries included approach (haven't tried). TypeORM had a lot of issues few years ago but might be getter better.
Disagree re: TypeScript though. Most libraries worth using have types or are TS native these days. I find myself much more productive writing TS on solo projects with less foot gunning.
Yeah despite being an interesting post about Scala, I came for the harrowing tale of a big deployment gone wrong. Downtime, angry customers, seat of the pants debugging and straight to prod gambles to save a sinking ship.
Instead, a smug tale of a huge upgrade that went unexpectedly smoothly - with a performance problem swiftly solved. Still a good story, and kudos to the team. Just not the horror show I came for.
The examples of strong opinions are really poor in the article. The one you've quoted isn't an opinion at all - nobody would prefer a nuisance over collaborative scheduling!
It's a shame because I do agree with the premise. Opinionated software is easy to use and therefore quickly carves out a niche with like-minded users.
We often hear about unpopular opinionated product decisions, but would love to read some good real examples where the PM has gone out on limb and it paid off.
We had the likes of Netscape Composer, Front Page and Dreamweaver. They produced mountains of un-maintainable and not non-compliant html code.
When HTML5 came along there was a big push for compliant sites. Also it made sense to have a developer use the power of CSS3 to handle layouts and responsiveness elegantly. So the WYSIWYG editors fell out of favour.
Months 12-24 is commonly a sweet spot IMO. A year is often enough to understand the domain and problem space well and be empowered to enact complex changes. It might taper off then a bit for some as they get bored or burn out, but a 2+ year tender is going to cover that very productive period and hopefully more.
If I were him I'd ask why not just print the spikes at the vaccine factory and inject them?
TBH I'm not sure if it's easier/cheaper to use the 3D-printers in our cells, or its more about accurate delivery to the right places, or something else.
I read thinking it is was just RNA molecules in the test tubes, but they added ribosomes (protein-based enzyme translation machinery) to the mix.
You could think of ribosomes and other cellular proteins as the system hardware and DNA/RNA the software.
Whilst this experiment is nonetheless interesting, even more so the 'RNA world' theory of how life evolved from just RNA molecules, functioning as both enzymes (ribozymes) and genetic material - code that _is_ the hardware, and built itself!
I agree with you in the sense that I only want to work places that recognize and value great code.
But everywhere has code that stinks. And it's hard to find people with the skills and experience to get rid if it. Before it can be gotten rid off, it must be understood.
In a sense it might be valuable to use the poor code in a reading screen. Firstly so we can agree it stinks, and the reasons why. And secondly, to find people with the attitude required to clean up messes that they didn't create (good scouts).
Even when the job is greenfield, or extending great code, I'd rather have engineers with the battle scars of doing tough maintenance.
I switched from dropbox to mega years ago when the former removed Linux support. TIL mega have version support so I need to enable that and try it out.
First thing I do on a new device is setup my mega shared drives - and there is a lot of plaintext files there!
As a small dev team we have a workflow to rapidly author tests integrating our internal and external graphql + rest APIs.
These tests can be run, tweaked and parameterized in various environments from the GUI, and then imported into our CI system with Newman. Its a low code approach that's saving us time so I'm grateful of the features we are getting (for free) with Postman.
For me there's a trade-off, depending on how often I setup a new machine. Value of automating with a procedural script vs taking the opportunity to try a leaner (or more modern) toolchain.
Currently upgrade about every 2-3 years, so I do tend not to need a bunch of things each iteration, and might upgrade OS. But I'd like a backup in case e.g. hardware failure, laptop lost or stolen.
Some declarative workstation config like terraform or Ansible would be interesting.
That sounds really neat is it some thing you can share? I recently setup a new machine which didn't take very long, but I have run into a few things I forget so would like to set up something similar.
I've always thought that the preparedness of employees to boot seniors out of their booked meeting rooms was a bellwether of good corporate culture. Places that values everyone's time and leaders follow process by example.