HN user

blystad

1 karma
Posts0
Comments3
View on HN
No posts found.

BARTEC PIXAVI | Oslo, Norway | ONSITE | https://www.pixavi.com

BARTEC PIXAVI creates smartphone for oil & gas, mining, shipping, chemical production and similar fields (rugged intrinsically safe ATEX/IEcx devices). The devices are used by almost all Fortune 500 energy companies, and they are manufactured in Norway. We're currently working on next generation of our smartphone, and we need your help!

We're currently hiring for two positions:

--- Backend + App developer --- This position is responsible for a new (greenfield) project for analysing telemetry data and customer bug reports (which include a lot of data). A big focus for the next generation is quality assurance, and reduced cost. You'll also be responsible for working on various apps that are shipped with the device, and used for over the air updates, and hardware testing (during manufacturing). And, if that isn't enough, you'll also assist with building software for automated hardware testing (software to control testing jigs, robot arms, analyse camera and sensor output, etc.). Some experience with statistical analysis is a bonus, but not a requirement (you can always ask your colleague with a PhD in mathematics).

Tech: Java/Kotlin; PostgreSQL (in our existing solutions, the new project can use whatever fits best); Docker; Kubernetes.

--- Mechanical Engineer --- You will have a unique chance to learn how to develop a smartphone and other mobile devices completely from scratch. We do almost everything in-house, you will be able to work on all the different product development phases. Everything from a new product proposal, concepts and prototyping, manufacturing and sourcing.

The position also assumes that you have experience with:

– CAD systems (Solidworks) as well as good technical and practical understanding. – Mechanical engineering and material science knowledge. – Production processes like: Injection molding, insert/over molding, CNC machining, die casting and sheet metal work. – FEM simulation capabilities is a benefit.

For more information, check out https://www.pixavi.com/company/employment/ Any questions can be sent to jobs {at} bartec-pixavi.com (or me, acb {at} bartec-pixavi.com ).

Hello,

As part of a school project in Software Engineering, I had to help my team understand and use Git.

Making them commit their work is fairly simple, that they can do with little guidance. The problems occour when they have merge conflicts.

We all worked in the same branch (stupid, I know, I didn't know better then) which created a lot of merge conflicts. The team had some issues fixing that in the beginning, but tools like SmartGit / SourceTree made their experience better.

Based on my limited experiences, I would recommend the following:

1 - Start with the simple parts, checking out code and committing.

2 - Then, introduce the concept of feature branches. Do not go all the way that Git flow does in the beginning, keep it simple for now, and then, when more of the organisation understands Git, you can go over to the full Git flow model. Ensure that people focus their branches, and let them only live for a short amount of time. This so that work can be synced up regularily.

3 - What can go wrong? Show them a somewhat advanced merge conflict and how you solved it.

4 - Try to introduce it to them using a GUI client (SourceTree / SmartGit) if they're not into the Command line. It can make adoption easier and less painful.

Good luck!