There are two words every designer needs to feel comfortable saying: “no” and “why.” Those words are the foundation of what we do. They’re the foundation of building an ethical framework.
There's an opinion going around how awesome game testing is - that you wake up knowing that you'll play games for 8 more hours, doing what you've been doing anyways while being unemployed, while gaining valuable experience to get a better job later on. This MIGHT be true in some ways, but not in all of them.
Software Engineers are rarely associated to Emotional Intelligence (EI). They are often seen as introverts who tend to focus inwards rather than outwards.
We know that if we do not get the requirements right, we will not get our projects right. But, how do we tell our sponsors that managing requirements is more than a box on our Work Breakdown Structure (WBS) and a line item on our list of activities? For those of us who have been given imposed deadlines that often seem arbitrary and unreasonable, managing requirements is the last thing on our minds. When the stress of trying to complete projects with tight deadlines seems overwhelming, it is more important than ever to ensure that we deliver a usable product.
The technology industry has been overloading the term ‘senior engineer’. A senior engineer is not a senior engineer is not a senior engineer. What “senior” really means depends on what your organization needs and how it operates.
Despite the fact that an ETL task is pretty challenging when it comes to loading Big Data, there’s still the scenario in which you can load terabytes of data from Postgres into BigQuery relatively easy and very efficiently. This is the case when you have a lot of immutable data distributed in tables by some timestamp. For example, a transactions table with a created_at timestamp column. BigQuery and Postgres have great tools in order to do this pretty fast and conveniently.