Good on you.
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.
87 karma · joined April 12, 2018
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.
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.
Salary: AUD140K+
Read more here: https://thevolte.com/page/jobs-senior-software-engineer Apply link: https://form.typeform.com/to/HYZvyc3i
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.
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.
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.
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.
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.
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!
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.
First thing I do on a new device is setup my mega shared drives - and there is a lot of plaintext files there!
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.
One of my peeves is a review that points out a bug/incorrectness without offering proof, or suggesting the fix/correct way. The reviewer might observe a code smell, but it's so much better dealt with a question-comment, e.g. "did you try?" vs "this looks wrong".
I generally aim to make every comment a question ("can we..."), and not make assumptions that the author didn't think of something already. Unless I just stating an objective fact that is clearly unknown e.g. "this duplicates library function x...".
If I know the queries that client apps are going to be running it would be useful to lock the API down to those. It sacrifices flexibility, but if you control apps and server, e.g. a startup then you still get the benefit of flexibility in development. Just need a system of add to the whitelist before deployment.
I have been looking for a way to achieve this with graphene but looks like there isn't a library for that yet. I'm wonder if other platforms offer this?
But no amount of layering makes the problem go away. Sometimes god-like keys are unavoidable. Those needed by Terraform etc are an example that comes to mind.
Could require a POST or maybe even HTTP DELETE to guard against woopsies. The latter has semantic niceness about it.
I like this approach, although risky if you mean you routinely replace the production db.
My preferred setup is to automate restores into a pre-prod environment, apply data masking and run tests there. It's not a replacement for full DR exercises, but at least it automates the backup verification process as part of your build system.
AWS provides a docker image for emulating DynamoDB which works great for local dev and will commonly be paired with lambdas.
Another option I have used recently for implementing node web services is https://github.com/apex/up which also has a nice local dev experience.
Was also thinking of customising the login greeting to mention the file (/etc/motd).
Like some others hear I'm more interested in the carbon cost of purchases. How long it takes to earn the cost is something my brain automatically calculates! (maybe younger folks don't do that).
I recently worked on an idea to try and build a movement to rally people around taking action to benefit the CO2 problem during a specific month of the year: https://march2zero.com