Перейти до основного вмісту

Work plan

Priority Skill Comments
9 Language STL, Iterators, Xml
4 Modeling UML Diagrams
3 Refactoring Code Smells
2 Code Quality Static code analyzing Working with test data, fixtures
0 Concurrency Local thread memory, thread specific data Thread pool concept
-2 Coaching
-7 SQL ,,,,,
-7 DB Design Transactions
-8 DB Access ADO or ODBC
-10 Estimation Work Break Down Structure

Design - OOD GRASP Patterns
Мітки:

Коментарі

Дописати коментар

Популярні дописи з цього блогу

ebusd and vailant ecotech plus plus controller

 ebusctl   localhost: find -c bai bai AccessoriesOne = no data stored bai AccessoriesTwo = no data stored bai ACRoomthermostat = no data stored bai AntiCondensValue = no data stored bai averageIgnitiontime = no data stored bai BlockTimeHcMax = no data stored bai BoilerType = no data stored bai ChangesDSN = no data stored bai CirPump = no data stored bai CodingResistor = no data stored bai CounterStartattempts1 = no data stored bai CounterStartattempts2 = no data stored bai CounterStartAttempts3 = no data stored bai CounterStartAttempts4 = no data stored bai currenterror = no data stored bai DateTime = no data stored bai dcfState = no data stored bai DCFTimeDate = no data stored bai DCRoomthermostat = on bai DeactivationsIFC = no data stored bai DeactivationsTemplimiter = no data stored bai DeltaFlowReturnMax = no data stored bai DisplayMode = no data stored bai DSN = no data stored bai DSNOffset = no data stored bai DSNStart = no data stored bai EBusHeatcontrol = no data store...
1 коментар
Докладніше

Home assistant - modbus - HHC-N8I8OP

Thanks to https://www.cncwiki.org/index.php?title=HHC-N8I8OP  I managed to connect this buggy module to home assistant using modbus integration: It is important to have verify delay big to not break logic.  modbus:   - type: tcp     host: 192.168.222.222     port: 5000     name: "modbus1"     switches:       - name: "hhc_r8"         address: 16         write_type: coil         verify:           delay: 36       - name: "hhc_r7"         address: 17         write_type: coil         verify:           delay: 37       - name: "hhc_r6"   ...
Дописати коментар
Докладніше

How to symbolicate crash logs in XCode organizer

If you have application distributed through Apple appstore or Testflight you should be able to get automatic crash reports by opening XCode/Window/Organizer menu, then select app and go to Crashes tab. If crashes are not symbolicated you can symbolicate them manually by: 1. In organizer, call for context menu by pressing on crash log call stack section 2. Select "show in finder ..." menu item 3. Navigate up to ~/Library/Developer/Xcode/Products/ [app bundle id]/ [app version]/Crashes/Appstore/ 4. Copy debug symbols there: 5. Go back to Organizer and select "Resymbolicate" context menu item on call stack area. Now you should be able to see symbolicated log. Works for me on XCode 10 and Testflight.
2 коментарі
Докладніше