jrmiii
I'm interested in hearing more about this - any resource you can point me at or do you mind elaborating a bit? TIA!
It's easy to draw parallels between what's described and those dysfunctions. In case you're not familiar, this framework by Patrick Lencioni outlines five obstacles that can mess up a team’s flow: absence of trust, fear of conflict, lack of commitment, avoidance of accountability, and inattention to results.
Particularly relevant to this situation: > Fear of conflict: seeking artificial harmony over constructive passionate debate
Just to warn you though, there is a tradeoff. You can also just act like an asshole and cite a culture of toxic positivity if people take issue with your behavior. The key is collaborate, productive focus on the outcomes with the other human beings involved in the endeavor.
[0] https://en.wikipedia.org/wiki/The_Five_Dysfunctions_of_a_Tea...
He mentioned this:
> With FLAME, your dev and test runners simply run on the local backend.
and this
> by default, FLAME ships with a LocalBackend
Can't wait for the deep dive on how that works
He's made the distinction in the article that those tools are great when you need durability, but this gives you a lower ceremony way to make it Just Work™ when all you're after is passing off the work.
For example, if I used the heroku api to do the equivalent of ps:scale to boot up more nodes - those new nodes (dynos in heroku parlance) could see what kind of pool members they are. I don't think there is a way to do dyno specific env vars - they apply at the app level.
If anyone tries to do a Heroku backend before I do, an alternative might be to use distinct process types in the Procfile for each named pool and ps:scale those to 0 or more.
Also, might need something like Supabase's libcluster_postgres[1] to fully pull it off.
EDIT2: So the heroku backend would be a challenge. You'd maybe have to use something like the formation api[2] to spawn the pool, but even then you can't idle them down because Heroku will try to start them back. I.e. there's no `restart: false` from what I can tell from the docs or you could use the dyno api[3] with a timeout set up front (no idle awareness)
[1] https://github.com/supabase/libcluster_postgres
[2] https://devcenter.heroku.com/articles/platform-api-reference...
[3] https://devcenter.heroku.com/articles/platform-api-reference...
Acknowledging this is brand new; just curious what your thinking is.
EDIT: Would it go in the pool config, and a runner as a member of the pool has access to that?
I'm trying to go through the same thought process - this is neat, how do i translate into more practical applications. It seems like such a powerful paradigm if one can figure out that mapping.
In other words, what resources do you wish existed?
The syntax is a bit different though, so it depends on where your source is coming from, see here: https://text-to-diagram.com/?example=sequence&b=mermaid
Here's an example that's been reposted, but with updates. https://news.ycombinator.com/item?id=36788210
> Please don't use HN primarily for promotion. It's ok to post your own stuff part of the time, but the primary use of the site should be for curiosity.
That being said, usually repost happen with substantially new information, perhaps OP should post what's new or what warrants the repost.
It's a philosophy I really align with, but seems somewhat antithetical to big-A Agile
Further, to me this sounds like the ideal work environment, but I've worked with folks who would consider this a frustrating experience with no clear direction.
It will be interesting what the privacy policy & controls will look like on something like this, particularly given the COPPA issues Amazon is recently dealing with.
https://www.aboutamazon.com/news/policy-news-views/amazon-re...
https://www.meetup.com/find/?keywords=hacker%20news&source=E...
It reminds me of that adage, "Start your business, the tool you build to run your business is now your business"
As a QA Automation Engineer you will be using our applications the way a user would by designing tests to hunt bugs and ensure we are meeting business requirements. By finding ways to test breaking application functionality and organizing and managing resolutions, you will be an integral part of the development team and on the front lines of developing the user experience.
EDUCATION AND EXPERIENCE REQUIREMENTS ● 2+ years of experience as a QA Analyst, Business Analyst, Automation Engineer and/or Software Developer ● Outstanding Organizational skills and attention to detail are key to success in this role ● Experience working on a Lean/Agile team ● Familiarity with testing types (e.g. backend, frontend, automation, usability, etc.) ● Testing experience using full stack integration testing, such as Cypress, Reflect, Playwright or Puppeteer ● Basic HTML, CSS, JavaScript ● Git & GitHub
BONUS SKILLS AND EXPERIENCE: ● Familiarity with Elixir and/or Phoenix ● User Experience (UX) sensibilities ● Experience in financial services
To apply, please submit resume to: joe_martinez (__at__) ucbi [/dot/] com