Seeking a full-time IC developer or manager role (contract terms negotiable).
With over 14 years of experience on product teams across diverse domains such as employee engagement, ed tech, personal finance, and legal tech, I have held various positions from individual contributor to tech lead, team lead, and development manager.
I am highly driven and possess the leadership skills necessary to build and lead high-performing teams.
I would love to connect and see if there's a potential match.
I recently took my Macbook to get a new battery at the Apple Store. While I was there, I asked for them to fix the lid as it was a little loose and was bugging me.
Not only did they not do it (they initially said no problem), they lied and told me I needed to replace the entire panel for $800 as it was a broken `spring` and could not be fixed.
I called bullshit and fixed it myself at home with a screw driver set.
I asked this question myself when I first started and I think some of these answers are a little too 'SF'. Drop me a line at joelthecoder@gmail.com and I would be happy to share and give feedback.
- 6-8 years of ETL development experience with an ETL tool such as: Informatica, DataStage, Ablnitio, or MS SSIS
- 6-8 years of experience developing reports with a BI tool such as MicroStrategy, Cognos, Business Objects, Birst, Tableau, etc. (tabular, dashboards, mobile, or visualization)
- 4-6 years of SQL experience
- Experience with relational databases (MySQL and Postgres preferred)
- Experience with dimensional modeling (dimensions, facts, star and snowflake schemas)
- Understanding of OLTP and OLAP , including their differences
- Understanding of data warehousing and ETL-specific concepts (landing, staging, lookups, aggregates, batches, transformations, DQ, SCDs, archiving, surrogates, ragged hierarchies, etc.)
- Ability to unit-test data (different from testing applications)
- Knowledge of performance and tuning techniques for data warehouses
- Experience gathering and documenting requirements
- B.S. or higher in Computer Science
- 1-5 years of experience with: HTML, PHP, CSS, Javascript/JQuery
- Experience in both software development and testing environments
- Web & Mobile Automation experience is a plus
- Familiarity with Selenium Web-Driver, Appium and Jenkins is a plus
- Co-op experience an asset
- Recent graduate from University or College with a degree in Computer Science or equivalent
People don't understand that admitting that you do not know does not mean you are dumb. It actually makes you dumb by not admitting it since you're wasting everyone's time by bullshitting and beating around the bush.
Actually, whether admitting it is dumb or not depends a lot on whether you're dealing with an objective or subjective situation, and the odds * costs of being caught at wrong answers.
For an example of a subjective situation, in a poker game it can be useful to pretend to know you will win in cases where it is unknown, or even in cases where you know you have a weak hand. The other player's subjective impression of what you know is more important than its actual accuracy.
On the other hand, computer programmers and engineers usually are dealing with objective circumstances where not admitting you don't know results in things breaking and delays finding out the objectively true answer.
A common failing is to not recognize which of the two types of situations you are in, and just assume you should treat it like the one you are most used to. Hence engineering types may be ignored because they don't sound confident in their answers, and political types forget that that rules or legislation cannot override the laws of physics.
I think this is the most important point left out of the article. How hard it is to admit that you don't know something is dependent on the costs of doing so. Sometimes it's harder to pretend you do know.
The better real world example isn't poker, but it comes up anytime you're talking with someone who knows less than you: your boss, customers, friends. The cost of being caught at wrong answers is often quite low.
And often the cost isn't only low to yourself, but to all parties involved. The article's author makes the leap to academic dishonesty right away. But, especially in this field of work, we talk a lot about the value of social skills over pure technical skills. BSing has a bad connotation but you can also think of it as consistently leaving good impressions or presenting things in the best light. It's not a rigid distinction.
A good example is the post below who said he probably got passed up for promotions because saying I don't know made the boss think he lacked "confidence". It's not surprising that the person in charge might disagree with the value of "I don't know". It's probably part of the social skill set that put him in charge in the first place.
Of course in the technical field the cost of a fudged truth can be very high, but the potential benefits are equally high, because you're often dealing with people who don't have the background to judge anything on its technical merits. The less knowledgeable they are, the more they have to rely on your presentation.
The "courage" to say I don't know is a good standard in academic and technical fields, but in the fields of business and politics (and social interactions in general!) it's not so clear-cut.
Remote: Yes
Willing to relocate: Unlikely
Technologies: JS, TS, React, Ruby, Python, PHP, MySQL, PostgreSQL, GraphQL, the usual web tech stack.
Résumé/CV: https://www.linkedin.com/in/joellanglois/
Email: joelthecoder@gmail.com
Seeking a full-time IC developer or manager role (contract terms negotiable).
With over 14 years of experience on product teams across diverse domains such as employee engagement, ed tech, personal finance, and legal tech, I have held various positions from individual contributor to tech lead, team lead, and development manager.
I am highly driven and possess the leadership skills necessary to build and lead high-performing teams.
I would love to connect and see if there's a potential match.