#lubridate — Public Fediverse posts

#Day29 | Uncertainties – Monochrome | #30DayChartChallenge | . Coffee Price Forecast — Holt-Winters (HW) Built with #RStats using #forecast, #ggplot2, #dplyr, #lubridate, #scales and #tidyr.

#Day29 | Uncertainties – Monochrome | #30DayChartChallenge | . Coffee Price Forecast — Holt-Winters (HW) Built with #RStats using #forecast, #ggplot2, #dplyr, #lubridate, #scales and #tidyr.

#Day29 | Uncertainties – Monochrome | #30DayChartChallenge | . Coffee Price Forecast — Holt-Winters (HW) Built with #RStats using #forecast, #ggplot2, #dplyr, #lubridate, #scales and #tidyr.

#Day29 | Uncertainties – Monochrome | #30DayChartChallenge | . Coffee Price Forecast — Holt-Winters (HW) Built with #RStats using #forecast, #ggplot2, #dplyr, #lubridate, #scales and #tidyr.

Ok, why do people keep doing this:

library(tidyverse)
library(lubridate)

when the first call automatically loads the package in the second call? Am I missing something here?

I see this **everywhere**!

#rlang #rlanguage #tidyverse #lubridate

Ok, why do people keep doing this:

library(tidyverse)
library(lubridate)

when the first call automatically loads the package in the second call? Am I missing something here?

I see this **everywhere**!

#rlang #rlanguage #tidyverse #lubridate

Ok, why do people keep doing this:

library(tidyverse)
library(lubridate)

when the first call automatically loads the package in the second call? Am I missing something here?

I see this **everywhere**!

#rlang #rlanguage #tidyverse #lubridate

Ok, why do people keep doing this:

library(tidyverse)
library(lubridate)

when the first call automatically loads the package in the second call? Am I missing something here?

I see this **everywhere**!

#rlang #rlanguage #tidyverse #lubridate

Ok, why do people keep doing this:

library(tidyverse)
library(lubridate)

when the first call automatically loads the package in the second call? Am I missing something here?

I see this **everywhere**!

#rlang #rlanguage #tidyverse #lubridate

Day 22 | Timeseries – Stars | #30DayChartChallenge. Visualization made with R using #ggplot2, #dplyr, #showtext, #lubridate and #cranlogs. | Source: cranlogs R Package.

Day 22 | Timeseries – Stars | #30DayChartChallenge. Visualization made with R using #ggplot2, #dplyr, #showtext, #lubridate and #cranlogs. | Source: cranlogs R Package.

Day 22 | Timeseries – Stars | #30DayChartChallenge. Visualization made with R using #ggplot2, #dplyr, #showtext, #lubridate and #cranlogs. | Source: cranlogs R Package.

Día 11 | Distribuciones – “Stripes” | #30DayChartChallenge. La visualización fue creada usando R basado en los paquetes: #ggplot2, #dplyr, #sf, #lubridate, #ggtext, #showtext, #RcolorBrewer, #rnaturalearth y #cowplot. Fuente: CHIRPS.

Día 11 | Distribuciones – “Stripes” | #30DayChartChallenge. La visualización fue creada usando R basado en los paquetes: #ggplot2, #dplyr, #sf, #lubridate, #ggtext, #showtext, #RcolorBrewer, #rnaturalearth y #cowplot. Fuente: CHIRPS.

Día 11 | Distribuciones – “Stripes” | #30DayChartChallenge. La visualización fue creada usando R basado en los paquetes: #ggplot2, #dplyr, #sf, #lubridate, #ggtext, #showtext, #RcolorBrewer, #rnaturalearth y #cowplot. Fuente: CHIRPS.

@danwwilson @lwpembleton #brms by @paul_buerkner has made Bayesian models incredibly fun and intuitive for me. I love the combination of well thought out defaults and API with a lot of depth and power, should you need it. Other than that, I think #lubridate needs some love! Oh and #igraph, which just works ™️ plus it's lovely descendant #tidygraph 🕸️
#packagelove

@danwwilson @lwpembleton #brms by @paul_buerkner has made Bayesian models incredibly fun and intuitive for me. I love the combination of well thought out defaults and API with a lot of depth and power, should you need it. Other than that, I think #lubridate needs some love! Oh and #igraph, which just works ™️ plus it's lovely descendant #tidygraph 🕸️
#packagelove

@danwwilson @lwpembleton #brms by @paul_buerkner has made Bayesian models incredibly fun and intuitive for me. I love the combination of well thought out defaults and API with a lot of depth and power, should you need it. Other than that, I think #lubridate needs some love! Oh and #igraph, which just works ™️ plus it's lovely descendant #tidygraph 🕸️
#packagelove

@danwwilson @lwpembleton #brms by @paul_buerkner has made Bayesian models incredibly fun and intuitive for me. I love the combination of well thought out defaults and API with a lot of depth and power, should you need it. Other than that, I think #lubridate needs some love! Oh and #igraph, which just works ™️ plus it's lovely descendant #tidygraph 🕸️
#packagelove

@danwwilson @lwpembleton #brms by @paul_buerkner has made Bayesian models incredibly fun and intuitive for me. I love the combination of well thought out defaults and API with a lot of depth and power, should you need it. Other than that, I think #lubridate needs some love! Oh and #igraph, which just works ™️ plus it's lovely descendant #tidygraph 🕸️
#packagelove

@antimnguyen The #tidyverse people strive to invent catchy names for their packages, I like #lubridate best, which simplifies arithmetics with date and time.

@antimnguyen The #tidyverse people strive to invent catchy names for their packages, I like #lubridate best, which simplifies arithmetics with date and time.

@antimnguyen The #tidyverse people strive to invent catchy names for their packages, I like #lubridate best, which simplifies arithmetics with date and time.

@antimnguyen The #tidyverse people strive to invent catchy names for their packages, I like #lubridate best, which simplifies arithmetics with date and time.

Working with Dates and time in #rstats ? Here's a brief intro to #lubridate
https://www.linkedin.com/learning/r-for-data-science-lunch-break-lessons/lubridate

Working with Dates and time in #rstats ? Here's a brief intro to #lubridate
https://www.linkedin.com/learning/r-for-data-science-lunch-break-lessons/lubridate