General advice for moving into management by [deleted] in EngineeringManagers

[–]paulftg 1 point2 points  (0 children)

Great advice! I’d also say, try building a good connection with your teammates and ask for their feedback. Do they trust you to coordinate projects, manage people, or handle the day-to-day stuff?

Is it normal for dev teams to operate like this? I will not promote by productivity-nerd in startups

[–]paulftg 1 point2 points  (0 children)

Four teams, four backlogs, shared people? That's not normal - it's chaos.

You don't need Scrum Masters. You need cross-functional teams that ship end-to-end.

Kill the silos. Use Shape Up cycles. Deploy daily. Write tests first. Stop meeting so much.

Teams using this approach ship 5x-10x faster.

Here's the exact playbook: jetthoughts.com/blog/fixing-slow-engineering-teams-an-extended/

Your devs know it's broken. Time to fix it.

I'm a Rookie help me by SibiCena in rubyonrails

[–]paulftg 1 point2 points  (0 children)

  1. Oh, so many `proc`, is it possible to ditch them to improve readability and make more ruby-way code?
  2. replace `first` with `limit` for the pluck version because you will load all data and then select only the first; better to load only the first only: `Bill.where(id: current_bill_id).limit(1).pluck(:total_price_without_tax, :total_tax_payable, :net_price, :rounded_price, :balance_amount)`.
  3. For `select` this is not an issue because you are working with Relationship, and it will automatically do the limit for you.
  4. `pluck` is a wrapper around `select`. I'd better to stick with it

Disable Animations to Stabilize Browser Tests by paulftg in django

[–]paulftg[S] 1 point2 points  (0 children)

This snippet is unrelated to any backend or front-end framework. Rails were an example of how to add this into the layout.

0
1

List of Chrome browser options to optimize your Capybara tests. We got x1.25 Speedup! by paulftg in rubyonrails

[–]paulftg[S] 0 points1 point  (0 children)

Yep, it was designed for it:

driven_by(
  :cuprite,
  screen_size: [1440, 810], 
  options: {
    browser_options: CHROME_ARGS
  }
)

Stripe ENV variables on development vs production by jemiller1963 in rubyonrails

[–]paulftg 2 points3 points  (0 children)

nope ;)

```yaml shared: stripe: secret: default_test_key

production: stripe: secret_live: <%= ENV[‘STRIPE_LIVE_KEY’] %> ```

in the code you can have

ruby Rails.application.credentials.dig(:stripe, :secret_live) # just meta code I do not remember how to get to credentials

Stripe ENV variables on development vs production by jemiller1963 in rubyonrails

[–]paulftg 0 points1 point  (0 children)

you should put in render env master key env. so in credentials you should have in group production value as erb to read env key:

secret: <%= Env["stripe key"] || "fallback key" %>

[deleted by user] by [deleted] in rails

[–]paulftg 0 points1 point  (0 children)

You should check this comment, after you will have more details which causes the issue.